AWS Removes NAT Gateway’s Dependence on Internet Gateway for Private Communications
You can now launch NAT Gateways in your Amazon Virtual Private Cloud (VPC) without associating an internet gateway to your VPC. Internet Gateway is required to provide internet access to the NAT Gateway. However, some customers use their NAT Gateways with Transit Gateway or virtual private gateway to communicate privately with other VPCs or on-premises environments and thus, do not need an internet gateway attached to their VPCs.
You can now launch NAT Gateways in your Amazon Virtual Private Cloud (VPC) without associating an internet gateway to your VPC. Internet Gateway is required to provide internet access to the NAT Gateway. However, some customers use their NAT Gateways with Transit Gateway or virtual private gateway to communicate privately with other VPCs or on-premises environments and thus, do not need an internet gateway attached to their VPCs.
A NAT Gateway enables instances in a private subnet to connect to services outside your VPC using the NAT Gateway’s IP address. With this feature, you can set the connectivity type to Private at the time of NAT Gateway creation. A private NAT Gateway, or NAT Gateway with connectivity type set to private, does not require EIP and you do not need to attach an internet gateway with your VPC. A Private NAT Gateway uses its private IP address to perform network address translation. You can route traffic from your Private NAT Gateway to other VPCs or on-premises network using Transit Gateway or virtual private gateway.
Private NAT Gateway is available in all AWS Regions except AWS GovCloud (US). To learn more about VPC NAT Gateway and this feature, please visit our documentation.