CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2amazon-elastic-beanstalkamazon-route53
Bill Noble
Bill Noble

Reputation: 6744

Use of Elastic IP address in Route 53 not working

I am trying to change which instance my A record in Route 53 points to.

For my domain app.mydomain.com the A record in Route 53 currently points to the elastic IP of one of my two instances (e.g. 11.22.33.44). This works fine. If I enter app.mydomain.com in a browser I get taken to the instance.

I have created a new elastic IP address for the other instance that I have in EC2 and put this IP address in the Route 53 A record in place of 11.22.33.44. Although the instance is working fine (i.e. I can enter mysecondinstance.elasticbeanstalk.com in a browser and get to see what I expect) if I enter app.mydomain.com in a browser the connection times out. I have left it over an hour since I made the change in Route 53.

Anyone know what I am doing wrong? I guess I am missing an important step somewhere?

Upvotes: 0

Views: 533

Answers (2)

Tal
Tal

Reputation: 7997

Elastic Beanstalk architecture (read this) provides a much simpler approach. You don't need to point your route 53 URL to the internal server, but rather to the Elastic Beanstalk load balancer. The latter will take care of routing traffic to the internal servers, and will replace them seamlessly in case of failure.
So to address your case - simply point your route 53 A record to the Elastic Beanstalk load balancer (elaborated here).

Upvotes: 1

Exelian
Exelian

Reputation: 5888

Not a direct answer to your question, but perhaps an interesting suggestions.

Instead of changing the A record (which takes time to propagate), you could reassociate the Elastic IP address to your new instance. This should only take a second or 5 and all traffic will automatically go to your new instance.

The only problem is that existing connections will be terminated, so if you do this for anything other than http(s) traffic, be careful that you close all connections!

Upvotes: 2

Related Questions