← All articlesInfra and cloud

AWS NAT Gateway cost: how to calculate and reduce it

The hourly rate is easy to spot. What inflates the bill is the per-gigabyte processing charge, and you can measure it in ten minutes.

Julien Mauclair · ~9 min · intermediate
StackAWSVPCNAT GatewayCloudWatch

An AWS NAT Gateway costs an hourly fee plus a charge for every gigabyte it processes, in both directions. In November 2026, in Paris, that is $0.050 per hour and $0.050 per GB, or $36.50 a month before a single byte moves. To cut the bill, route traffic to S3 and DynamoDB through a free gateway endpoint.

What really drives the cost up is traffic to AWS services that goes through the gateway when a VPC endpoint would avoid it. Prices come from the price file AWS published on November 7, 2026.

01What you actually pay for

The VPC pricing page lists three lines. The first is the provisioned gateway hour: any partial hour is billed as a full one, whether traffic flows or not. The second is data processing: every gigabyte that crosses the gateway is billed, whatever its source and destination. The third is standard EC2 data transfer, on top of the other two: egress to the internet, and traffic crossing from one Availability Zone to another.

The part that surprises most people: processing also applies to traffic that stays inside AWS. The official example on the pricing page sends 1 GB from an instance to an S3 bucket in the same region. The transfer is free, but the gateway still charges its $0.045 processing fee at the Ohio rate. AWS adds that this charge goes away with a gateway endpoint, which has neither hourly nor processing fees.

Rates vary by region. Read on November 7, 2026 in the AWS NAT Gateway price file:

Two extra charges are easy to miss. A public gateway uses a public IPv4 address, and AWS bills every public IPv4 address associated with a resource in the VPC: $0.005 per hour in Paris according to the AmazonVPC price list. And if an instance sends its traffic to a gateway in another zone, that cross-zone transfer is billed, while it is free within the same zone.

The new regional NAT gateway does not change the unit price: it is billed per hour for each zone it runs in. Across three zones, the AWS example gives $0.045 times three, or $0.135 per hour in Ohio.

02The formula, reworked on a real case

With 730 hours in a month, the Paris formula reads:

nat-cost-paris.txtTEXTCopy
monthly cost = number of gateways × 730 h × ($0.050 + $0.005 for IPv4)
+ GB processed × $0.050
+ data transfer out to the internet
+ cross-zone transfer, if an instance uses a gateway in another zone

Take a typical VPC across three zones, with one gateway per zone as AWS recommends for resilience, and 2,000 GB processed in the month. All prices are Paris rates in November 2026, from the AWS price files cited above.

3 gateways × 730 h × [$0.050](https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/natgateway.json)$109.50
3 IPv4 addresses × 730 h × [$0.005](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonVPC/current/region_index.json)$10.95
2,000 GB × [$0.050](https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/natgateway.json)$100.00
Total before data transfer out, [Paris rates](https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/natgateway.json)$220.45

Here the fixed fee weighs slightly more than the traffic. But processing grows with activity and the fee does not: at 10,000 GB, the processing line reaches $500 at the Paris rate while the fixed part stays at $120.45. If half of those 2,000 GB go to S3 buckets in the same region, a gateway endpoint removes 1,000 GB × $0.050, or $50 a month, at no cost.

This calculation leaves out data transfer to the internet, which depends on volume and region. In the pricing page example, internet egress is counted at $0.09 per GB in Ohio, on top of gateway processing. That amount does not go away with a VPC endpoint: only traffic to AWS services benefits.

03Measure your traffic before changing anything

Do not start from a guess: measure the volume, then where it goes. AWS recommends that order in its article on reducing NAT charges: identify the traffic sources first, then act.

Step 1: the volume, with CloudWatch

Gateways publish their metrics under the AWS/NATGateway namespace, listed by CloudWatch. According to the metrics documentation, BytesOutToDestination counts what goes out to the destination and BytesInFromDestination what comes back, with Sum as the useful statistic. CloudWatch keeps this data for 15 months, so you can look at last month.

nat-volume.shBASHCopy
# Bytes sent to destinations, per day, for October
aws cloudwatch get-metric-statistics --region eu-west-3 \
--namespace AWS/NATGateway --metric-name BytesOutToDestination \
--dimensions Name=NatGatewayId,Value=nat-0123456789abcdef0 \
--start-time 2026-10-01T00:00:00Z --end-time 2026-11-01T00:00:00Z \
--period 86400 --statistics Sum
# Same command with the response metric
aws cloudwatch get-metric-statistics --region eu-west-3 \
--namespace AWS/NATGateway --metric-name BytesInFromDestination \
--dimensions Name=NatGatewayId,Value=nat-0123456789abcdef0 \
--start-time 2026-10-01T00:00:00Z --end-time 2026-11-01T00:00:00Z \
--period 86400 --statistics Sum

Add both series and divide by 1,073,741,824 to get gigabytes. It is an estimate of the processed volume, to compare with the bill line. A regional gateway adds the AvailabilityZone dimension, per the same page. In Cost Explorer, then group by usage type on the EC2-Other service: gateway lines carry the region prefix and the word NatGateway. The exact label can vary, so check it in your own account.

Step 2: the destination, with flow logs

Volume alone does not tell you what to fix. Turn on VPC flow logs to CloudWatch Logs, then run the queries from the Logs Insights documentation. Replace x.x.x.x with the gateway's private IP and y.y with the first two octets of your VPC CIDR.

nat-top-sources.txtTEXTCopy
filter (dstAddr like 'x.x.x.x' and srcAddr like 'y.y.')
| stats sum(bytes) as bytesTransferred by srcAddr, dstAddr
| sort bytesTransferred desc
| limit 10
nat-top-downloads.txtTEXTCopy
filter (dstAddr like 'x.x.x.x' and srcAddr not like 'y.y.')
| stats sum(bytes) as bytesTransferred by srcAddr, dstAddr
| sort bytesTransferred desc
| limit 10

The first query shows the instances sending the most. The second shows the external addresses returning the most data. Match those addresses against the ranges AWS publishes to tell whether it is S3, a container registry or a genuine external service. Remember to turn flow logs off or shorten their retention after the analysis: they cost money too.

04Cut the bill: the order to follow

1. Gateway endpoints for S3 and DynamoDB

This comes first because it is free: a gateway endpoint has no hourly fee and no processing fee. It only exists for S3 and DynamoDB, and only in the region where you create it. For a bucket in another region, AWS points to an S3 interface endpoint.

s3-endpoint.shBASHCopy
aws ec2 create-vpc-endpoint --region eu-west-3 \
--vpc-id vpc-0123456789abcdef0 \
--service-name com.amazonaws.eu-west-3.s3 \
--route-table-ids rtb-0aaaaaaaaaaaaaaaa rtb-0bbbbbbbbbbbbbbbb

Gateway is the command's default endpoint type. Pass every route table of your private subnets, otherwise part of the traffic keeps going through the gateway. Without a policy, AWS attaches a full-access one: restrict it if your security rules require it. Do the same for DynamoDB with the service name com.amazonaws.eu-west-3.dynamodb.

2. Interface endpoints, only past the break-even point

For other AWS services, an interface endpoint also bypasses the gateway, but it is not free: billed per hour for each zone it is provisioned in, plus a per-GB fee. In Paris, AWS lists $0.011 per hour and $0.01 per GB for the first petabyte, according to the AmazonVPC price list read in November 2026.

The break-even calculation for a given service: each GB sent through the endpoint instead of the gateway saves $0.050 minus $0.01, so $0.04. The fixed cost is 730 h × $0.011, or $8.03 per zone per month. The threshold is the fixed cost divided by $0.04:

1 zone ([$8.03 a month](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonVPC/current/region_index.json))about 201 GB per service per month
2 zones ([$16.06 a month](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonVPC/current/region_index.json))about 402 GB per service per month
3 zones ([$24.09 a month](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonVPC/current/region_index.json))about 603 GB per service per month

Below the threshold, the gateway stays cheaper for that service. This only counts processing: if the gateway sits in another zone than your instances, the cross-zone transfer you avoid makes the endpoint pay off a little sooner. Redo the math with your region's rates, they are not the same everywhere.

3. Match gateways to zones

AWS advises checking that the resources sending the most traffic sit in the same zone as their gateway, since transfer within a zone is free. Trusted Advisor has a dedicated check for this zone independence. The opposite question also comes up: a single gateway for three zones saves two fees, or 2 × 730 h × $0.055 = $80.30 a month in Paris. In return, traffic from the other two zones pays cross-zone transfer, and an outage in that zone cuts internet egress for the whole VPC.

Staging, low trafficOne gateway, losing a zone is acceptable
Production, low trafficOne gateway per zone, the fee buys resilience
Production, heavy traffic to AWSEndpoints first, then one gateway per zone
Heavy traffic to the internetOne gateway per zone, and work on the volume itself

4. Delete what you no longer use

A gateway forgotten in a test VPC costs its fee as long as it exists: AWS notes that billing only stops when you delete it. List them once a quarter with aws ec2 describe-nat-gateways in every region you use, and compare with the ActiveConnectionCount metric. A value of zero for weeks is a good candidate for deletion.

The NAT Gateway is one of the items covered in the 5 lines that wreck your bill. For the overall method, see cut an AWS bill in half, and for the starting network architecture, hosting your SaaS on AWS. If you want an outside look at your bill and architecture, that is what Stralya does.

Worth noting

The prices quoted are those of November 7, 2026. AWS publishes them in files that are updated regularly: redo the math with current prices before deciding.

05FAQ

Why does my NAT Gateway cost more than my instances?

Because processing is billed per gigabyte, in both directions, including traffic to S3 and other AWS services in the same region. A job that downloads a lot of data or container images pushes this line up without touching instance size. Measure the volume with CloudWatch, then its destination with flow logs.

Is an S3 VPC endpoint really free?

The gateway endpoint is: AWS states it has no hourly or processing fees. Only the S3 interface endpoint is paid, by the hour and by the GB. The gateway endpoint only works for buckets in the same region.

Can I get rid of the NAT Gateway entirely?

Yes, if your private resources never need to reach the internet and everything they call on AWS goes through endpoints. In that case, compare the cost of the interface endpoints you need with the gateway's, using the threshold worked out above. As soon as an external dependency is called, such as a payment API, you need internet egress.

Is the regional NAT gateway cheaper?

Not per unit: it is billed per hour for each active zone, at the same hourly rate as a regular gateway in the AWS example. Its benefit is simpler management, and its billing adjusts when it drops a zone. The formula stays the same.

06Sources

Sources & further reading
In short

Measure the processed volume and where it goes first, then create the S3 and DynamoDB gateway endpoints, which cost nothing. Keep interface endpoints for the services that cross the break-even point worked out here.

Talk about your project ↗
Julien MauclairJulien Mauclair is the co-founder and CTO of Klickbee, where he builds the agency’s websites, tracking and AI automations, and develops Klickbee Tracking. He also runs Stralya, which designs and runs AWS infrastructure for scale-ups. Before that, he built the entire AWS infrastructure of an e-commerce business, since sold.

Read next