- Newest
- Most votes
- Most comments
Since the end of 2025, you have an additional option with the Amazon VPC Regional NAT Gateway, described and introduced in the following link by AWS. This means you no longer need to carefully ensure that the route with 0.0.0.0/0 in a private subnet is routed to the relevant NAT-Gateway within the same Availability Zone. This avoids cross-Availability Zone traffic and prevents misconfiguration and potential issues:
A Nat Gateway needs an internet gateway to route to the internet. You need different route tables for the private and public subnets
Please see example of how NAT Gateways and Internet Gateways should be setup
Public Route Table
| Destination | Target |
|---|---|
| 0.0.0.0/0 | igw-id |
Private Route Table
| Destination | Target |
|---|---|
| 0.0.0.0/0 | nat-gateway-id |
https://docs.aws.amazon.com/vpc/latest/userguide/vpc-example-private-subnets-nat.html
Relevant content
asked 2 years ago
asked 8 months ago
- AWS OFFICIALUpdated 9 months ago
