NAT gateway pricing explained
A NAT gateway costs $0.045 per hour it exists plus $0.045 per GB of data it processes, in us-east-1 at the time of writing, which is $32.85 a month before any traffic. The processing charge applies to every byte in either direction, and data that then leaves AWS also pays normal data transfer out.
Pricing dimensions
| Dimension | Unit | us-east-1 price |
|---|---|---|
| NAT gateway | hour (or partial hour) | $0.045 |
| Data processed | GB | $0.045 |
| Data transfer out to the internet (charged in addition) | GB, first 10 TB | $0.09 |
| Cross-AZ traffic to a NAT gateway in another zone | GB, each direction | $0.01 |
From the AWS Price List API at the time of writing. The hourly charge runs whether or not anything uses the gateway, and each NAT gateway is billed separately, so one per Availability Zone triples the fixed cost.
Worked examples
1. One gateway, light traffic. 500 GB a month of software updates and API calls to the internet:
- Hours: 730 × $0.045 = $32.85
- Processing: 500 × $0.045 = $22.50
- Data out after the 100 GB free allowance: 400 × $0.09 = $36.00
- Total: $91.35, of which $55.35 is the NAT gateway itself
2. Highly available setup. Three gateways, one per AZ, processing 2 TB in total: 3 × $32.85 = $98.55 plus 2,048 × $0.045 = $92.16, $190.71 before data transfer out.
3. S3 traffic through NAT. A data pipeline in private subnets reading 5 TB a month from S3 in the same Region via the NAT gateway pays 5,120 × $0.045 = $230.40 in processing alone. A gateway VPC endpoint for S3 carries the same traffic for nothing.
What is free and what is not
- Traffic between resources inside the VPC never touches the NAT gateway.
- Gateway endpoints for S3 and DynamoDB have no hourly or per-GB charge and take that traffic off the NAT gateway.
- Interface endpoints (PrivateLink) for other services are cheaper per GB than NAT processing but have an hourly charge per AZ; see VPC endpoint pricing.
- Inbound responses are processed too: a 1 GB download through the gateway is 1 GB processed.
Common surprises
- Container image pulls from ECR or Docker Hub on every scale-out.
- Lambda functions in a VPC calling public AWS endpoints.
- Logs and metrics agents shipping to an external provider.
- A private subnet routed to a NAT gateway in a different AZ, adding cross-AZ charges on top.
- Forgotten gateways in test VPCs, each $32.85 a month for nothing.
Finding NAT cost on the bill
NAT gateways sit under "EC2-Other" in Cost Explorer. Group by Usage type and look for NatGateway-Hours and NatGateway-Bytes (other Regions add a prefix such as EUW2-). To see which gateway, use the BytesOutToDestination and BytesInFromDestination CloudWatch metrics per gateway, and VPC Flow Logs to find the busiest source addresses. The PacketsDropCount alarm covers the reliability side.
Cutting it: reducing NAT gateway cost and NatGateway-Bytes explained.
Questions
How much does a NAT gateway cost per month?
About $32.85 for the hours alone in us-east-1 at the time of writing ($0.045 × 730), plus $0.045 per GB processed.
Is NAT gateway data processing charged both ways?
Yes. Bytes sent out and responses coming back through the gateway both count as data processed.
Does S3 traffic through a NAT gateway cost money?
Yes, $0.045 per GB processed. A free gateway VPC endpoint for S3 removes that charge for same-Region buckets.
Is a NAT instance cheaper than a NAT gateway?
A small EC2 instance doing NAT has no per-GB processing fee, so it can be cheaper for heavy traffic, but you take on patching, scaling and availability yourself.
NAT charges grow quietly with traffic, so a sudden jump usually means a new workload is pulling data through it. CloudConsole is being built to show costs and alarms on a phone.
About the app → · Download on the App Store