- 新しい順
- 投票が多い順
- コメントが多い順
- Yes, you are correct. The Internet Gateway does the NATing between the Public and Private IPs.
- Yes, it is possible to use a Public CIDR range for the VPC but you still will need an Internet Gateway.
See: Modify the IP addressing behavior of your subnets
"... however, you can use publicly routable CIDR blocks for your VPC. Regardless of the IP address range of your VPC, we do not support direct access to the internet from your VPC's CIDR block, including a publicly-routable CIDR block. You must set up internet access through a gateway; for example..."
Thank you for clarifying it. I must say it wasn't clear at all and is also a big surprise coming from the world of linode and digital ocean where each VM just gets public ip. Anyway this leads to another question if you don't mind. Is there a way for me to get this public CIDR range from amazon? I mean short of bringing my own routable space to AWS? I don't mind the gateway between instance and the internet, but I do mind the NAT. The protocol I'm dealing with - SIP - doesn't cope well with address mangling. In other words my project requires me to have direct (meaning no NAT, routing gateway is OK) connectivity. How can I do it with AWS? Thanks
関連するコンテンツ
- AWS公式更新しました 3年前