Hidden cost · Last verified 2026-08-25

NAT gateway processing

Traffic through a managed NAT gateway is billed per processed gigabyte in addition to internet egress.

Official pricing: Source

This item is not in the current price snapshot. No rate is shown.

NAT is a processing meter that sits in front of internet egress, not a substitute for it. Amazon VPC bills a NAT Gateway for every hour the gateway exists and for every gigabyte that crosses it, inbound or outbound, then still bills Data Transfer Out if the packet leaves AWS. A private subnet that pulls container images from a public registry can therefore show three line items for one download: NAT time, NAT processing, and internet out. Gateway-type VPC endpoints for S3 and DynamoDB are the documented way to take that AWS API traffic off NAT; those endpoint SKUs are not in this snapshot, which is why this page prints no NAT rate. Azure NAT Gateway and Google Cloud NAT use the same two-part idea of time plus processed volume, with their own units, on their pricing pages. DigitalOcean does not sell a separate NAT Gateway SKU; outbound sits inside the Droplet transfer cap until overage. Cloudflare R2 traffic never traverses a customer NAT. Confirm hour and per-gigabyte processing units at https://aws.amazon.com/vpc/pricing/ https://azure.microsoft.com/pricing/details/azure-nat-gateway/ and https://cloud.google.com/nat/pricing before you treat an egress-only calculator as a private-subnet bill.