Overview
Load Balancer Server using NGINX
Load balancing across multiple application instances is a commonly used technique for optimizing resource utilization, maximizing throughput, reducing latency, scalability and ensuring fault-tolerant configurations.
Load Balancer Methods:
Round-robin: Requests to the application servers are distributed in a round-robin fashion.
Least-connected: Next request is assigned to the server with the least number of active connections.
IP-hash: A hash-function is used to determine what server should be selected for the next request based on the clients IP address.
Session persistence: With ip-hash, the clients IP address is used as a hashing key to determine what server in a server group should be selected for the clients requests. This method ensures that the requests from the same client will always be directed to the same server.
Weighted load balancing: It is also possible to influence Nginx load balancing algorithms even further by using server weights
Reverse proxy implementation in Nginx includes load balancing for HTTP, HTTPS, FastCGI, uwsgi, SCGI, memcached, and gRPC
Load balancing health checks:
NGINX can continually test your HTTP upstream servers, avoid the servers that have failed, and gracefully add the recovered servers into the load balanced group.
Passive Health Checks Health check a URI Define Custom Conditions Test your TCP upstream servers UDP Health Checks
Highlights
- Load balance traffic across multiple application instances using difference load balance methods / metrics
- Load balancing support for load balancing for HTTP, HTTPS, FastCGI, uwsgi, SCGI, memcached, and gRPC
- NGINX can continually test your HTTP upstream servers, avoid the servers that have failed, and gracefully add the recovered servers into the load-balanced group. Providing constant up-time for your applications
Details
Typical total price
$0.082/hour
Pricing
- ...
Instance type | Product cost/hour | EC2 cost/hour | Total/hour |
---|---|---|---|
t2.nano | $0.036 | $0.006 | $0.042 |
t2.micro AWS Free Tier | $0.036 | $0.012 | $0.048 |
t2.small | $0.036 | $0.023 | $0.059 |
t2.medium Recommended | $0.036 | $0.046 | $0.082 |
t2.large | $0.036 | $0.093 | $0.129 |
t2.xlarge | $0.036 | $0.186 | $0.222 |
t2.2xlarge | $0.036 | $0.371 | $0.407 |
t3.nano | $0.036 | $0.005 | $0.041 |
t3.micro AWS Free Tier | $0.036 | $0.01 | $0.046 |
t3.small | $0.036 | $0.021 | $0.057 |
Additional AWS infrastructure costs
Type | Cost |
---|---|
EBS General Purpose SSD (gp2) volumes | $0.10/per GB/month of provisioned storage |
Vendor refund policy
We do not currently support refunds, but you can cancel at any time.
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Latest OS Patches installed. Simply run an update on your terminal to install the latest OS updates. "sudo apt-get update"
Additional details
Usage instructions
Scroll down to 'Getting Started' on the following URL: https://cloudinfrastructureservices.co.uk/how-to-setup-nginx-on-ubuntu-in-azure-aws-gcp/
Resources
Vendor resources
Support
Vendor support
Email support, contact us through our website or leave a comment on our getting started guide
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.