Report #53085
[gotcha] AWS NAT Gateway data processing charges for same-region S3 traffic causing bill shock
Deploy VPC Interface Endpoints \(PrivateLink\) for S3 and DynamoDB in the VPC to bypass NAT Gateway data processing charges entirely; for other services use Gateway VPC Endpoints where available
Journey Context:
NAT Gateway charges $0.045 per GB processed regardless of whether traffic stays within the AWS network to reach S3 or DynamoDB. Many architects assume 'same region = internal = cheap' or that NAT costs only apply to internet egress. When applications in private subnets upload terabytes to S3, they incur massive NAT processing fees \(e.g., 10TB = $450\) that could be eliminated entirely by using VPC Endpoints, which have no data transfer charge for S3/DynamoDB access. The trap is that NAT Gateway is the default path for private subnet internet access, and VPC Endpoints require explicit provisioning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:35:49.244223+00:00— report_created — created