AWS NAT Gateway Pricing in 2026: The Direct Answer
NAT Gateway costs $0.045 per hour and $0.045 per GB processed in us-east-1 (N. Virginia). With ~730 hours/month, the hourly fee alone is ~$32.85/month per gateway regardless of traffic. The per-GB charge stacks on top — 100 GB processed = $4.50.
NAT Gateway Pricing by Region (Per Hour / Per GB)
- us-east-1 / us-east-2 / us-west-2 — $0.045 / $0.045 (cheapest)
- us-west-1 / eu-west-1 / eu-west-2 / eu-west-3 — $0.048 / $0.048
- eu-central-1 (Frankfurt) — $0.052 / $0.052
- ap-south-1 (Mumbai) — $0.056 / $0.056
- ap-southeast-1 (Singapore) — $0.059 / $0.059
- ap-northeast-1 (Tokyo) — $0.062 / $0.062
- sa-east-1 (São Paulo) — $0.093 / $0.093 (most expensive — 2× the US price)
Why NAT Gateway Bills Get Out of Control
Three things stack: (1) running one gateway per AZ for high availability (3 AZs = 3× the hourly fee = ~$100/mo before any data), (2) container workloads pulling images from ECR and uploading logs over the NAT, and (3) cross-AZ traffic between services. Add separate per-GB data transfer charges ($0.09/GB outbound to internet for the first 10 TB) on top.
Cheaper Alternatives to NAT Gateway
- VPC Endpoints (Gateway type) — free for S3 and DynamoDB. Eliminates NAT Gateway charges for traffic to those services. Usually the #1 quick win.
- VPC Endpoints (Interface type) — $0.01/hr/endpoint for ECR, KMS, SSM, etc. Cheaper than NAT Gateway when you process more than ~22 GB/month through those services.
- NAT Instances — your own EC2 doing NAT. Cheaper for low traffic (small t4g instance ~$3-5/mo) but you manage HA and patching.
- IPv6 + Egress-Only Internet Gateway — free, but requires IPv6-capable services on both ends.
- AWS PrivateLink — direct private connection to other VPCs/services without NAT.
Most teams save 30–60% on NAT Gateway costs just by adding gateway endpoints for S3 and ECR. If you're running EKS or any container-heavy stack, this is likely the highest-ROI single change you can make.