# Why is my NAT Gateway bill so high?

AWS cost guides · Updated 17 November 2026

**Short answer:** A NAT gateway bills for every hour it exists and for every gigabyte it processes, in either direction, on top of normal data transfer. A big bill nearly always means a lot of traffic from private subnets is going through it, often to S3, DynamoDB, ECR or other AWS APIs that could use a VPC endpoint instead, or crossing Availability Zones to reach a NAT gateway in another zone.

## How the charge is calculated

There are two meters, plus whatever data transfer the traffic would have cost anyway:

| Meter | Usage type | Scales with |
|---|---|---|
| NAT gateway hours | `EUW2-NatGateway-Hours` | Number of NAT gateways x hours provisioned. A partial hour bills as a full hour. |
| Data processed | `EUW2-NatGateway-Bytes` | Every GB that passes through, whatever the source or destination. |
| Data transfer | `EUW2-DataTransfer-Out-Bytes`, `EUW2-DataTransfer-Regional-Bytes` | Internet egress, and cross-AZ hops between your instance and the NAT gateway. |

The prefix is the Region billing code (`EUW2` is eu-west-2). The VPC pricing page's worked example, for US East (Ohio), uses $0.045 per NAT gateway-hour and $0.045 per GB processed at the time of writing; check your Region on the [pricing page](https://aws.amazon.com/vpc/pricing/). A regional NAT gateway is billed per hour for each Availability Zone it is active in.

In Cost Explorer these lines sit under the service **EC2 - Other**, not under VPC, which is why many people miss them.

## Find what is sending the traffic

1. In Cost Explorer, filter Service = EC2 - Other, group by Usage type, daily. Compare `NatGateway-Bytes` with `NatGateway-Hours`: hours are flat and predictable, bytes are where surprises live.
2. Find which gateway is busy with the `AWS/NATGateway` metrics `BytesOutToDestination` and `BytesInFromDestination`.
3. Turn on VPC flow logs for the NAT gateway's network interface and sum bytes by source and destination address. The [flow logs query page](https://cloudconsole.dev/logs-insights/vpc-flow-logs-rejected-traffic) shows the query shape; group by `srcAddr, dstAddr` instead of filtering on REJECT.

```
# Bytes sent out to destinations by one NAT gateway, per day, last 7 days
aws cloudwatch get-metric-statistics --namespace AWS/NATGateway \
  --metric-name BytesOutToDestination \
  --dimensions Name=NatGatewayId,Value=nat-0123456789abcdef0 \
  --start-time 2026-11-10T00:00:00Z --end-time 2026-11-17T00:00:00Z \
  --period 86400 --statistics Sum --region eu-west-2

# NAT gateway cost by usage type this month
aws ce get-cost-and-usage --region us-east-1 \
  --time-period Start=2026-11-01,End=2026-11-17 \
  --granularity MONTHLY --metrics UnblendedCost \
  --filter '{"Dimensions":{"Key":"USAGE_TYPE_GROUP","Values":["EC2: NAT Gateway - Data Processed","EC2: NAT Gateway - Running Hours"]}}' \
  --group-by Type=DIMENSION,Key=USAGE_TYPE
```

If the top destinations resolve to S3 or DynamoDB addresses in the same Region, you have found the cheapest fix.

## Safe ways to reduce it (biggest saving first)

1. **Add S3 and DynamoDB gateway endpoints.** Gateway endpoints have no hourly or data processing charge, and traffic to those services in the same Region stops touching the NAT gateway once the route tables are associated.
2. **Use interface endpoints for heavy AWS API traffic** such as ECR image pulls, CloudWatch Logs or STS. Interface endpoints have their own hourly and per-GB charges, so they pay off only above a certain volume; see [VPC endpoint cost](https://cloudconsole.dev/aws-pricing/vpc-endpoint-pricing).
3. **Keep traffic in its own zone.** If instances in eu-west-2b route through a NAT gateway in eu-west-2a you pay processing plus cross-AZ transfer. One NAT gateway per AZ, with each private subnet routed to its local one, removes the cross-AZ part.
4. **Cut chatty egress**: cache container images and package downloads, and check for retry loops or log shippers sending to an external endpoint.
5. **Delete NAT gateways in dev VPCs that nothing uses**, after checking the route tables that point at them.

```
# S3 gateway endpoint for a VPC, attached to the private route tables
aws ec2 create-vpc-endpoint --vpc-id vpc-0123456789abcdef0 \
  --vpc-endpoint-type Gateway \
  --service-name com.amazonaws.eu-west-2.s3 \
  --route-table-ids rtb-0123456789abcdef0 rtb-0fedcba9876543210
```

## What not to do

- Do not delete a NAT gateway without checking which private route tables point at it; workloads lose outbound access immediately.
- Do not put an interface endpoint in every AZ of every VPC for low-traffic services. You can end up paying more in endpoint-hours than you saved in processing.
- Do not collapse to a single shared NAT gateway to save hours unless you accept the zone dependency and the cross-AZ transfer it adds.
- Do not assume S3 traffic is free because S3 is "in AWS". Through a NAT gateway it is billed as processed data.

## Questions

### Why is my NAT gateway charging me with no traffic?

The hourly charge applies for every hour the gateway is provisioned and available, even with zero bytes processed. Only deleting it stops that charge.

### Does a gateway endpoint for S3 cost anything?

No. AWS documents no hourly or data processing charge for gateway endpoints, which exist only for S3 and DynamoDB.

### Is there a free tier for NAT gateway?

No free tier allowance for NAT gateway hours or processing is listed on the VPC pricing page.

### Where do NAT gateway charges appear in Cost Explorer?

Under the EC2 - Other service, with usage types ending in NatGateway-Hours and NatGateway-Bytes.

## When this happens away from your desk

NAT gateway processing creeps up quietly as traffic grows. CloudConsole, a phone app for AWS, shows spend by service and usage type, and explains what a line such as NatGateway-Bytes means, so you can spot the climb from your phone.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Amazon VPC pricing](https://aws.amazon.com/vpc/pricing/)
- [Pricing for NAT gateways](https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-pricing.html)
- [How do I reduce data transfer charges for my NAT gateway?](https://repost.aws/knowledge-center/vpc-reduce-nat-gateway-transfer-costs)

## Related

- [NAT gateway pricing explained](https://cloudconsole.dev/aws-pricing/nat-gateway-pricing)
- [NatGateway-Bytes and NatGateway-Hours](https://cloudconsole.dev/costs/natgateway-bytes)
- [VPC endpoint pricing explained](https://cloudconsole.dev/aws-pricing/vpc-endpoint-pricing)
- [AWS data transfer cost between Availability Zones](https://cloudconsole.dev/costs/cross-az-data-transfer-cost)
- [What is "EC2 - Other" on my AWS bill?](https://cloudconsole.dev/costs/ec2-other-costs)
- [CloudWatch alarm: NAT Gateway ErrorPortAllocation](https://cloudconsole.dev/alarms/nat-gateway-errorportallocation)
- [Why is my AWS bill so high?](https://cloudconsole.dev/how-to/why-is-my-aws-bill-so-high)

---

Source: https://cloudconsole.dev/costs/nat-gateway-cost

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
