- 新しい順
- 投票が多い順
- コメントが多い順
EIP's are associated to private IPv4 addresses on ENI's. From the docs:
Each private IPv4 address can be associated with a single Elastic IP address, and vice versa.
The instance size will determine how many ENI's can be associated, and how many IP addresses can be assigned to each ENI. This is documented here.
In a /24 subnet you've got more than enough address space for the 10 private addresses you'll need to assign and associate EIP's with. You'll want to make sure the instance type you choose has not just the number of IP's you'd expect to associate today, but to plan for growth as well.
Other considerations you should think through, too, include protecting this instance with a firewall and ensuring the ability to auto-scale if needed.
I understood the default EIP associating policy cannot do this, but we should have the chance to do this multiple EIP's to one private IP mapping if I use AWS Firewall. Is this possible? In my on-prem Fortigate firewall, I can do this mapping easily.
関連するコンテンツ
- 質問済み 6年前
No, that's not possible. AWS Network Firewall doesn't provide any NAT functionality.
Can you be specific as to which firewall? I'm assuming you're talking about AWS WAF, not AWS Network Firewall, but want to be sure. An Elastic Load Balancer might be the best approach here, depending on architecture.