AWS NAT Gateway Pricing Calculator
Quantify NAT Gateway hourly + per-GB processing and cross-AZ surcharges before your VPC bill surprises you. us-east-1 list pricing.
- No signup
- Instant results
- ~2 min
NAT Gateway footprint
us-east-1 rates (June 2026): $0.045/hr per gateway plus $0.045/GB processed. Cross-AZ traffic adds $0.02/GB round-trip.
EC2 calculator · Cloud cost rollup
Who This Tool Is For
Platform engineers and FinOps leads sizing VPC egress for EKS, Lambda-in-VPC, or classic three-tier apps. If Cost Explorer shows a climbing EC2-Other or VPC line item, NAT is often the culprit.
Why We Built This Tool
NAT Gateway pricing is simple on paper but expensive in aggregate: hourly per gateway plus per-GB processed adds up fast when microservices chat across AZs. We built this to mirror the us-east-1 rate card we use in client VPC reviews.
What Problem It Solves
- Hourly + GB math. Combine gateway count, uptime, and processed GB in one view.
- Cross-AZ visibility. Model hairpin traffic that doubles networking charges.
- HA planning. See the cost of one NAT per AZ before you commit.
- Budget defensibility. Export-friendly numbers for finance and architecture reviews.
Pair with our cloud cost optimization engagement or the EC2 Pricing Calculator for compute alongside networking.
Frequently Asked Questions
Where do these prices come from?
AWS NAT Gateway us-east-1 list prices as of June 2026: $0.045 per gateway-hour and $0.045 per GB processed, plus $0.02/GB for cross-AZ data transfer associated with NAT paths. Confirm in the AWS Pricing Calculator before budgeting.
Does this include PrivateLink or Transit Gateway?
No — this calculator covers NAT Gateway hourly and processing charges plus modeled cross-AZ GB. Transit Gateway attachments, VPN, Direct Connect, and interface endpoint hourly fees are separate line items.
Why run NAT in every AZ?
Routing private subnet egress through a NAT in the same AZ avoids cross-AZ data charges and removes a single-AZ failure domain for outbound traffic. The tradeoff is more hourly gateway fees.
Can I avoid NAT entirely?
For AWS API traffic, VPC endpoints often remove the need for NAT. For general internet egress you still need NAT, egress VPC, or IPv6 egress-only paths — each with different cost and ops profiles.
How accurate is this estimate?
Arithmetic matches published us-east-1 rates for the inputs you provide. Actual bills add flow logs, public IPv4 charges, and endpoint fees — use this for directional budgeting.