Loading page content
Estimate what NAT Gateways cost you on AWS: the hourly charge per gateway plus per-gigabyte data processing, and see what VPC endpoints would save.
Real AWS NAT Gateway cost includes two components most people forget about: an hourly per-AZ charge and per-GB data processing. This calc compares both against the VPC endpoint alternative so you can decide if you should switch.
Switch saves $68.60/mo (78%). Annualized: $823/yr.
Caveats: cross-AZ data ($0.01/GB) is not modeled. Per-region pricing varies; this uses us-east-1 published rates. The most common scenario where NAT wins is bursty, low-volume egress to many destinations.
NAT Gateway is one of the most reliably surprising line items on an AWS bill, for two reasons. The hourly charge applies per gateway, and multi-AZ high availability means three of them, so a workload processing almost no traffic still accrues a meaningful fixed monthly cost. Then data processing is charged per gigabyte on top, and it is charged in addition to normal data transfer, not instead of it.
The largest single saving available to most accounts is a gateway VPC endpoint for S3 and DynamoDB. Those are free, and they route that traffic off the NAT Gateway entirely, and for a great many workloads, S3 traffic is the majority of what was flowing through it. Interface endpoints for other services cost money but frequently still beat NAT data processing charges at volume.