Part of the appeal of cloud computing is the promise of greater uptime. To achieve that, all parts of your architecture must be highly available, including the load balancer. Now you can achieve high availability (HA) for NGINX Plus on AWS with a new solution that combines
keepalived and the AWS Elastic IP address feature.
One widely used approach for HA on AWS is to put Elastic Load Balancer (ELB) in front of NGINX Plus instances. While this approach can be a good starting point, using ELB not only increases complexity and cost, but also imposes the following limitations:
- ELB does not expose a static IP address, which is critical requirement for some applications.
- ELB IP addresses are published using a DNS
CNAMErecord; you cannot map a root domain (for example, example.com) to a
CNAMEunless you delegate all DNS to Route 53.
- ELB does not support UDP, so you cannot take advantage of NGINX Plus’ UDP load balancing.
- ELB doesn’t scale quickly, so large traffic spikes can result in dropped traffic.
To avoid these limitations, our solution eliminates ELB in favor of a combination of
keepalived and an AWS Elastic IP address. An Elastic IP address is a single static IP address assigned to an active‑passive pair of NGINX Plus instances. If the master NGINX Plus instance goes out of service,
keeaplived automatically promotes the backup instance to master and transfers the Elastic IP address to it as shown in the figure.
New to NGINX Plus on AWS? Try it free for 30 days. For links to the available AMIs, see Installing NGINX Plus on Amazon EC2.