AWS NAT Gateway pricing: the per-GB cost and how to cut it.

·Updated · 5 min read · aws · finops

It's not the $33–38/month idle fee. It's the $0.045–0.052 per GB of traffic that never needed to leave the VPC. Most AWS accounts pay this tax silently, every month, on TBs of S3 reads.

AWS NAT Gateway pricing by region

A NAT Gateway has two charges: a fixed hourly fee for every hour it exists, and a data processing fee for every GB that passes through it. In each region the two prices are the same number. On-demand prices from the AWS price list, checked October 2026:

RegionPer hourPer month (730 h)Per GB processed
US East (N. Virginia) us-east-1$0.045$32.85$0.045
US West (Oregon) us-west-2$0.045$32.85$0.045
Europe (Stockholm) eu-north-1$0.046$33.58$0.046
Europe (Ireland) eu-west-1$0.048$35.04$0.048
Europe (London) eu-west-2$0.050$36.50$0.050
Europe (Milan) eu-south-1$0.050$36.50$0.050
Europe (Frankfurt) eu-central-1$0.052$37.96$0.052

One gateway, sitting idle, for a year: about $394 in us-east-1 and $456 in Frankfurt. That's the part everyone budgets for, and it's rarely the problem.

The problem is the per-GB. AWS bills you $0.045 per GB processed in each direction, on top of any data-transfer-out charges to the internet. If your private-subnet workloads pull 5 TB/month of container images from public ECR, npm packages, OS updates, S3 objects in another region, or — most often — S3 objects in the same region via the public S3 endpoint, that's another $225/month per gateway just for shovelling bytes you already had a free path to.

Multiply by 3 AZs × 4 environments and the tax adds up fast.

The killer: S3 over the public endpoint

The single biggest line item we see, in account after account, is private workloads reading from S3 over the public endpoint. The traffic stays within AWS, but because it's destined for a public IP, it routes through your NAT Gateway and you pay $0.045/GB for the privilege.

The fix is free, has been since 2015, and most accounts still don't use it: VPC gateway endpoints for S3 and DynamoDB. They cost nothing. They route traffic over AWS's private backbone. They take ten lines of Terraform.

resource "aws_vpc_endpoint" "s3" {
  vpc_id            = aws_vpc.main.id
  service_name      = "com.amazonaws.${var.region}.s3"
  vpc_endpoint_type = "Gateway"
  route_table_ids   = aws_route_table.private[*].id
}

resource "aws_vpc_endpoint" "dynamodb" {
  vpc_id            = aws_vpc.main.id
  service_name      = "com.amazonaws.${var.region}.dynamodb"
  vpc_endpoint_type = "Gateway"
  route_table_ids   = aws_route_table.private[*].id
}

Apply it. Your S3 traffic now bypasses the NAT Gateway entirely and AWS still charges you nothing for the endpoint. We've seen this single change cut NAT bills by 60–80% in data-heavy workloads.

The audit query

Before you optimise anything, look at what your gateways are actually processing. Pull the last 30 days from CloudWatch:

aws cloudwatch get-metric-statistics \
  --namespace AWS/NATGateway \
  --metric-name BytesOutToDestination \
  --dimensions Name=NatGatewayId,Value=nat-0abc123 \
  --start-time "$(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S)" \
  --end-time "$(date -u +%Y-%m-%dT%H:%M:%S)" \
  --period 86400 \
  --statistics Sum

Repeat with BytesInFromDestination, add the two sums, divide by 1e9 for GB and multiply by your region's per-GB price (for example 0.052 in Frankfurt). That's the monthly processing cost of this one gateway. Anything over a few hundred GB/day is worth investigating.

For "what is actually going through it", VPC Flow Logs is the only honest answer. Enable them, ship to S3 + Athena, and run:

SELECT
  dstaddr,
  SUM(bytes) / 1e9 AS gb_out
FROM vpc_flow_logs
WHERE srcaddr LIKE '10.%'
  AND dstaddr NOT LIKE '10.%'
  AND day >= date_add('day', -7, current_date)
GROUP BY dstaddr
ORDER BY gb_out DESC
LIMIT 20;

The top 20 destinations tell you exactly what to fix. S3 IPs (look up the prefix list com.amazonaws.global.s3) → add a gateway endpoint. ECR Public → switch to private ECR with an interface endpoint. Container registries on Docker Hub → mirror into ECR.

When one NAT per AZ is overkill

The AWS reference architecture says: one NAT Gateway per AZ, for HA. For most non-prod environments and many low-traffic prods, this is overkill — and triples your idle cost for failure modes you'd survive a brief blip on.

For dev and staging, a single shared NAT Gateway is usually fine. If the AZ it lives in goes down, your dev environment loses egress for an hour. Compare that to 3 × $32 × 12 = $1,150/year per environment forever.

For production, the calculation depends on what "egress down for one AZ" means for you. If your workload is mostly serving requests (egress is OS updates and metric pushes), you can survive a single-NAT outage. If it's ETL pulling from external APIs, you can't.

How to stop paying for a NAT Gateway (safely)

There is no "stop" or "pause" for a NAT Gateway: AWS bills it for every hour it exists, so the only way to stop the charge is to delete it. Before you do, make sure nothing still needs it.

  1. Find what routes through it. In the VPC console, open Route tables and look for routes with the NAT Gateway as target. Every subnet associated with those tables loses outbound internet access when the gateway goes.
  2. Check what those subnets actually call. Use the flow-log query above. If the traffic is mostly S3 or DynamoDB, a gateway endpoint replaces it for free; if it's ECR, Secrets Manager or other AWS APIs, interface endpoints may be enough.
  3. Decide where the remaining egress goes. For non-production, one shared NAT Gateway per VPC is usually fine. Workloads that never call the internet need nothing.
  4. Delete it, then release the Elastic IP. Deleting the gateway does not release its Elastic IP, and AWS charges for public IPv4 addresses whether they are in use or not (VPC pricing).
  5. Remove it from Terraform too. Otherwise the next terraform apply recreates it.

The IPv6 escape hatch

NAT Gateway exists because IPv4 is scarce. Workloads using IPv6 don't need it — they use an egress-only Internet Gateway, which has no hourly fee and no per-GB charge.

Going IPv6-first is a bigger architecture decision than this post can cover, but if you're starting greenfield in 2026 it's worth seriously considering. AWS has steadily rolled out IPv6 support across services; most managed AWS services and Kubernetes (with amazon-vpc-cni in IPv6 mode) support it now.

The five-minute checklist

  1. Add S3 + DynamoDB gateway endpoints to every VPC. Free, no risk, ten lines.
  2. Look at NAT bytes over 30 days per gateway. Anything > 1 TB/month deserves a flow-log investigation.
  3. For ECR-heavy workloads (CI runners, k8s nodes) add an ECR interface endpoint.
  4. Collapse non-prod NAT to one shared gateway per environment.
  5. Mirror Docker Hub / public package registries into private ECR with image cache.
Sanity check. Open Cost Explorer, group by usage type, filter to NatGateway-Bytes. If that line is more than 5% of your monthly AWS bill, you have at least one of the problems above and the fix is an afternoon's work.

If your NAT line looks worrying, our one-week cloud audit finds this and every other cost leak, and ends with one page on what to fix first.

Frequently asked questions

Can I stop or pause an AWS NAT Gateway?

No. A NAT Gateway is billed for every hour it exists, so the only way to stop the charge is to delete it. Check which route tables use it first, then release its Elastic IP after deleting, because public IPv4 addresses are charged separately.

How much does an AWS NAT Gateway cost per month?

An idle NAT Gateway costs about $32.85 a month in us-east-1 ($0.045 per hour × 730 hours) and about $37.96 in Frankfurt ($0.052 per hour). On top of that you pay $0.045 to $0.052 for every GB it processes, which is usually the larger part of the bill.

Is NAT Gateway data processing charged on top of data transfer?

Yes. The per-GB processing charge applies to all traffic through the gateway, and regular data transfer charges (for example to the internet or another region) are added on top.

How do I reduce NAT Gateway costs?

Add free gateway endpoints for S3 and DynamoDB, use interface endpoints for heavy AWS service traffic such as ECR, share one NAT Gateway in non-production environments, and use IPv6 with an egress-only internet gateway where you can.

Tell us what you need