---
title: "NAT Gateway and Data Transfer: The AWS Costs Nobody Owns"
description: "NAT Gateway processing and cross-AZ traffic rarely top the bill, but they grow quietly and nobody owns them. How to find them in the CUR and the design changes that remove most of them."
doc_version: 1.0.0
last_updated: 2026-10-02
date_published: 2026-07-14
canonical: https://ccx.hu/blog/aws-nat-gateway-data-transfer-costs
---

# NAT Gateway and Data Transfer: The AWS Costs Nobody Owns

> NAT Gateway processing and cross-AZ traffic rarely top the bill, but they grow quietly and nobody owns them. How to find them in the CUR and the design changes that remove most of them.

![NAT Gateway and Data Transfer: The AWS Costs Nobody Owns](https://s3.us-east-1.amazonaws.com/ccx.hu/images/14-nat-gateway-data-transfer.png)

Ask a team who owns the EC2 bill and someone will answer. Ask who owns the NAT Gateway line, or the cross-AZ data transfer line, and the room goes quiet. These charges rarely top the invoice, but they grow with every new service, every container image pull and every chatty microservice, and because they belong to the network rather than to a workload, nobody is accountable for them. In most estates we review, they are among the easiest savings to find and the quickest to fix.

## Where the money goes

Four charges do most of the damage:

- **NAT Gateway data processing.** Every gigabyte that passes through a NAT Gateway is charged a processing fee, on top of the gateway's hourly charge and on top of any data transfer charge for the same bytes. At roughly $0.045 to $0.05 per GB depending on region, a workload pulling a few terabytes a month through NAT adds up fast.
- **Cross-AZ data transfer.** Traffic between Availability Zones in the same region is charged per GB in each direction. A service in one AZ calling a database or cache in another, all day, is a steady line item that looks like nothing in any single hour.
- **Data transfer out to the internet.** Charged per GB in tiers. Usually expected, sometimes not: logs shipped to an external SaaS, backups copied off-platform, or APIs serving large responses without a CDN.
- **Public IPv4 addresses.** Since February 2024, every public IPv4 address is charged by the hour, whether attached or idle. Estates with hundreds of instances carrying public IPs they do not need pay for each one.

The common thread is that none of these is a resource a team consciously creates. They are side effects of architecture decisions made for other reasons.

## Finding them in the Cost and Usage Report

Cost Explorer will show you the totals. To find out *which* traffic is responsible, go to the Cost and Usage Report and group by usage type. Network charges have recognisable usage type names, prefixed with a region code:

```sql
-- Network-related usage by type and account, one billing period.
-- Replace cur2 with your Data Export table name.
SELECT
  line_item_usage_account_id      AS account,
  line_item_usage_type            AS usage_type,
  ROUND(SUM(line_item_usage_amount), 1)     AS gb_or_hours,
  ROUND(SUM(line_item_unblended_cost), 2)   AS cost
FROM cur2
WHERE billing_period = '2026-09'
  AND (   line_item_usage_type LIKE '%NatGateway%'
       OR line_item_usage_type LIKE '%DataTransfer-Regional-Bytes%'
       OR line_item_usage_type LIKE '%DataTransfer-Out-Bytes%'
       OR line_item_usage_type LIKE '%PublicIPv4%')
GROUP BY 1, 2
ORDER BY cost DESC;
```

`NatGateway-Bytes` is the processing charge, `NatGateway-Hours` the hourly charge, and `DataTransfer-Regional-Bytes` is cross-AZ traffic. The account breakdown usually points straight at the two or three VPCs responsible.

The CUR tells you *where*, but not *what*. For that, turn on VPC Flow Logs for the subnets behind the expensive NAT Gateways for a few days, send them to S3, and query by destination. Flow logs have their own cost, so scope them and switch them off once you have your answer. The destinations almost always fall into a handful of buckets: S3, ECR, other AWS service APIs, a monitoring or logging vendor, and a package mirror.

## Fix 1: gateway endpoints for S3 and DynamoDB

The single most common finding: workloads in private subnets reading from and writing to S3 through a NAT Gateway, paying the NAT processing fee on every byte.

**Gateway VPC endpoints for S3 and DynamoDB are free.** They add a route to your route tables so traffic to those services stays on the AWS network and skips the NAT Gateway entirely. There is no hourly charge and no per-GB charge.

```hcl
resource "aws_vpc_endpoint" "s3" {
  vpc_id            = aws_vpc.main.id
  service_name      = "com.amazonaws.eu-central-1.s3"
  vpc_endpoint_type = "Gateway"
  route_table_ids   = aws_route_table.private[*].id
}
```

If your private subnets talk to S3 and you do not have this, it is very likely the cheapest saving in your account. Add an endpoint policy if you want to restrict which buckets can be reached, which also helps against data exfiltration.

## Fix 2: interface endpoints where the volume justifies them

Other AWS services (ECR, CloudWatch Logs, Secrets Manager, STS, SSM and many more) are reached through **interface endpoints** (PrivateLink). These are not free: each endpoint has an hourly charge per AZ and a per-GB charge, but the per-GB charge is much lower than NAT processing.

So the decision is arithmetic. For high-volume services it pays off quickly; for a service you call a few times an hour, the endpoint's hourly charge across three AZs can cost more than the NAT traffic it replaces.

The usual winners:

- **ECR**, if you run containers. Every node pulling images through NAT pays processing on every layer. Note that ECR stores image layers in S3, so you need the `ecr.api` and `ecr.dkr` interface endpoints *and* the S3 gateway endpoint.
- **CloudWatch Logs**, for workloads that log heavily.
- **STS and SSM**, mostly for security and reliability reasons, with cost as a bonus.

In a multi-account estate, consider centralising interface endpoints in a shared networking VPC and resolving them from spoke VPCs through Transit Gateway and Route 53 Resolver rules. That turns many sets of endpoints into one, though it adds Transit Gateway data processing charges, so model both before committing.

## Fix 3: keep traffic in its Availability Zone

Cross-AZ charges come from three patterns:

- **A single NAT Gateway shared by all AZs.** Saves an hourly charge, then pays cross-AZ transfer on every byte from the other zones, and makes that one AZ a single point of failure for egress. One NAT Gateway per AZ, with each private subnet routing to the gateway in its own zone, is usually both cheaper at volume and more resilient.
- **Load balancers and service meshes spreading requests across zones.** Cross-zone load balancing is on by default for Application Load Balancers. For high-throughput internal services, availability-zone-aware routing in the client or mesh keeps most calls in-zone while still failing over.
- **Chatty data stores across zones.** Read replicas, caches and brokers placed in one AZ but read from all three. Where the client supports it, prefer the replica or node in the caller's zone.

Do not sacrifice multi-AZ resilience to save transfer charges. The goal is that steady-state traffic stays local and cross-AZ traffic happens on failover, not on every request.

## Fix 4: egress you did not mean to pay for

- **Put CloudFront in front of public content and APIs with large responses.** Transfer from AWS origins to CloudFront is not charged, and CloudFront's own transfer pricing and caching usually beat direct data transfer out.
- **Check what is shipping logs and metrics off-platform.** Third-party observability agents sending full-fidelity logs from every node can be a material egress line. Filter and sample at the source.
- **Release public IPv4 addresses that do not need to exist.** Instances in public subnets that never accept inbound traffic, idle Elastic IPs, and load balancers that could be internal. Query the CUR for `PublicIPv4` usage types to see the count per account, then use VPC IP Address Manager's public IP insights to find the specific addresses.

## Make it somebody's job

Network cost stays invisible because it lands in shared networking accounts. Two changes stop it drifting back:

- **Split shared networking cost back to consumers** using Cost Categories split charges, proportional to each business unit's usage. Teams start asking about NAT charges when the charges appear on their own showback.
- **Add network usage types to anomaly detection** for the networking account, so a new service pulling terabytes through NAT is caught in days, not on the next invoice.

## What this looks like at ccX

Data transfer and network design is one of the six levers in our [two-week AWS Cost Optimization Review](https://ccx.hu/aws-cost-optimization). We break network charges down by usage type and account, trace the expensive flows to their sources, and give you a prioritised list of endpoint, routing and placement changes with an annual saving estimate for each. Most estates have at least one change on that list that costs nothing to make. Fixed fee, read-only access, never a percentage of savings.

If nobody can tell you what your NAT Gateways are carrying, [book a 30-minute scoping call](https://ccx.hu/book).

## Where to go from here

- [AWS cost allocation that survives real teams](https://ccx.hu/blog/aws-cost-allocation-tagging-and-showback) - how to give shared network cost an owner.
- [AWS Cost Optimization Review](https://ccx.hu/aws-cost-optimization) - the full engagement.
- [Contact us](https://ccx.hu/contact)

> *AWS data transfer and endpoint pricing varies by region and changes over time. Check current rates for your regions before modelling savings.*

---

## Sitemap

- [Read this post on the web](https://ccx.hu/blog/aws-nat-gateway-data-transfer-costs)
- [All blog posts](https://ccx.hu/blog)
- [Full site map](https://ccx.hu/sitemap.md)
- [Home](https://ccx.hu/)
- [Services](https://ccx.hu/services)
- [EU AI Act Compliance](https://ccx.hu/eu-ai-act)
- [AWS GenAI Production Readiness](https://ccx.hu/aws-genai-review)
- [Glossary](https://ccx.hu/glossary)
- [Contact](https://ccx.hu/contact)
