I am running a single instance Elastic Beanstalk environment with an EC2 instance and MySql RDS.
The documentation for applying a website update without down time is geared to multi instance environments. The premise is that you create a new environment in Elastic Beanstalk and then switch the CNAMEs which mitigates the down time.
What are the steps for ensuring no down time for a single instance environment?
For multi instance environments, Route53 for the domain us set up with a record pointing to the IP address of the load balancer. In my case, I have followed the instructions and pointed it to the Elastic IP of the EC2 instance.
When I create a new Elastic Beanstalk environment to configure the new version of my website, it will have a new Elastic IP, so the configuration of Route53 will need updating.
I can't just change the Elastic IP specified within Route53 to the new EC2's Elastic IP in order to switch, because people will still be being directed to the old EC2 Elastic IP because of the TTL (time to live) on the DNS record.
How can I set it up so that I can direct visitors to my domain to the new EC2 instance straight away without the use of a load balancer IP?