将弹性IP连接到EC2弹性豆stal的实例
我的生产和开发应用程序正在EBS的EC2实例上运行，我需要将弹性IP附加到每个实例上。我能够将弹性IP与每个实例相关联，但是一段时间后，由于应用程序负载余额，IPS自动拆分，从而创建了EC2的新实例，我知道这是由于应用程序负载造成的，但我想知道如何持续存在弹性IPS到每个实例？我正在使用第三方集成，其中我必须发送静态IP使它们被列入白色。
My production and development application are running on EBS's EC2 instances where I need to attach an elastic IP to each instance. I am able to associate the elastic IPs to each instance but after some time the IPs disassociated automatically due to application load balance which creates a new instance of EC2, I know it's due to Application Loadbalance but I want to know how can I persist the elastic IPs to each instance? I am using third party integration in which I have to send my static IPs to make them whitelisted.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在自动缩放环境中运行时，用于从固定的IP（或固定IP的固定集）向第三方发送请求的AWS解决方案是创建 nat Gateway 在您的公共子网中（或每个公共子网中的一个），将弹性IPS分配给NAT网关，然后放置您EC2在私人子网中具有通往NAT网关的路线。
在此配置中，所有出站请求将通过NAT网关，该NAT网关将具有静态（弹性）IP，可以由第三方列入白色。
The AWS solution for sending requests to third parties from a fixed IP (or fixed set of IPs) when running in an auto-scaled environment is to create a NAT Gateway in your public subnet (or one in each public subnet), assign Elastic IPs to the NAT Gateways, and place your EC2 instances in private subnets with a route to the NAT Gateway.
In this configuration, all outbound requests will go through the NAT Gateway(s) which will have static (Elastic) IPs that can be whitelisted by third-parties.