amazon-web-services - 在AWS中保留相同的弹性IP和ENI集(Retain the same set of Elastic IP and ENI in AWS)

Question

I'm working on a project where the nodes are heavily dependent on static networking as it's kind of a static cluster.

(我正在做一个项目，其中节点在很大程度上依赖于静态网络，因为它是一个静态集群。)

Here it goes, there are 3 nodes in the cluster and are in auto-scaling but max count is 3 as the application running on top of them doesn't have the ability to scale automatically.

(顺便说一句，集群中有3个节点，它们正在自动扩展，但是最大数量为3，因为在它们之上运行的应用程序无法自动扩展。)

Have created three Elastic IPs and keeping a track/maintaining it programatically.

(已经创建了三个弹性IP并以编程方式对其进行跟踪/维护。)

Likewise, for the ENIs wanted to have some mapping created to EIP (manual is also fine) only once.

(同样，对于ENI，只希望一次创建一些到EIP的映射 （手动也可以）。)

So that once any new node comes up, it attaches to it's EIP by the program I wrote and as EIP is mapped to ENI, it will automatically attach to it.

(这样，一旦出现任何新节点，它就会通过我编写的程序附加到它的EIP上，并且当EIP映射到ENI时，它将自动附加到它上。)

I understand that Elastic IP is just a floating public IP which remains constant and ENI is a network interface for the EC2 .

(我知道弹性IP只是一个浮动的公共IP，它保持不变，而ENI是EC2的网络接口 。)

Just curious if there is something out there which can make this work, which will reduce my pain of updating R53 everytime a new node joins the cluster.

(只是想知道是否有什么可以使这项工作正常进行，这将减轻我每次新节点加入集群时更新R53的痛苦。)

Thanks in advance.

(提前致谢。)

  ask by jagatjyoti translate from so

Answer 1

Relying on IP is not the best design as you are already facing the challenges associated to it.

(依靠IP并非最佳设计，因为您已经面临与之相关的挑战。)

You should switch to hostnames, which are static in nature.

(您应该切换到主机名，该主机名本质上是静态的。)

You can configure and publish hostnames, which can remain the same but the mapped IP behind the scenes can change.

(您可以配置和发布主机名，这些主机名可以保持不变，但后台的映射IP可以更改。)

Yes you can utilize Route 53 in AWS to add A records for domain name to IP address mapping.

(是的，您可以利用AWS中的Route 53将域名的A记录添加到IP地址映射。)