在Route 53中使用弹性IP地址不起作用 [英] Use of Elastic IP address in Route 53 not working

问题描述

我正在尝试更改我在Route 53中的A记录所指向的实例.

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

对于我的域app.mydomain.com，Route 53中的A记录当前指向我的两个实例之一的弹性IP(例如11.22.33.44).这很好.如果我在浏览器中输入app.mydomain.com，则会进入该实例.

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.

我为EC2中的其他实例创建了一个新的弹性IP地址，并将此IP地址放置在Route 53 A记录中，代替了11.22.33.44.尽管实例运行良好(例如，我可以在浏览器中输入mysecondinstance.elasticbeanstalk.com并查看我的期望)，但如果我在浏览器中输入app.mydomain.com则连接超时.自从对Route 53进行更改以来，我已经离开了一个多小时.

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?

推荐答案

Elastic Beanstalk体系结构(在这里详细说明).

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).

这篇关于在Route 53中使用弹性IP地址不起作用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！