Report #97240
[gotcha] NAT Gateway bill is huge even though traffic stayed inside AWS
Route S3, DynamoDB, and other supported services through gateway VPC endpoints instead of NAT Gateway; keep NAT traffic in the same Availability Zone to avoid cross-AZ data charges.
Journey Context:
NAT Gateway charges per gigabyte processed regardless of destination, including traffic to S3 or other AWS services. Gateway VPC endpoints for S3 and DynamoDB are free \(no hourly or data-processing charge\), but interface endpoints are not. Cross-AZ NAT traffic also incurs charges. Teams often add a NAT Gateway for convenience and are surprised when high-volume S3 traffic generates a large processing bill that a VPC endpoint would eliminate.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T04:46:49.871178+00:00— report_created — created