Nginx Plus can be run in a 2 node HA cluster as a replacement for ELBs. Please see my previous previous post on situations where it might make sense to use Nginx Plus instead of AWS ELB services.
Below are the steps for launching an Nginx Plus cluster in Classic EC2:
If you have used AWS Elastic Load Balancers before, you might have come across this note while creating a new ELB:
Because the set of IP addresses associated with a LoadBalancer can change over time, you should never create an “A” record with any specific IP address. If you want to use a friendly DNS name for your load balancer instead of the name generated by the Elastic Load Balancing service, you should create a CNAME record for the LoadBalancer DNS name, or use Amazon Route 53 to create a hosted zone. For more information, see Using Domain Names With Elastic Load Balancing.
While CNAMEs would be suitable for most use cases, there are certain situations where CNAMEs do not fit business requirements. Like,
Most of us have a business requirement to change system passwords regularly and when we do, it usually ends up in a mess. Thankfully, Apache CloudStack has an API that allows you to modify XenServer host passwords without mucking around the database and encryption.
The API to change XenServer host password is updateHostPassword which you can use via CloudMonkey CLI tool. The steps to change the XenServer password would roughly be as below: