FixedmarkAWS NAT Gateway cost calculator
In us-east-1 an AWS NAT Gateway costs $0.045 per hour, $0.045 per GB processed, and $0.005 per hour for its public IPv4 address. Two AZs cost about $73 per month before traffic. Enter your traffic to see the monthly total next to a planned Fixedmark plan.
AWS rates checked October 2026 from the Amazon VPC pricing page (NAT Gateway and public IPv4) and the EC2 on-demand pricing page (data transfer). Confirm current prices with AWS. The estimate ignores free tiers and volume discounts.
| NAT Gateway hours (2 × $0.045/hr × 730 hr) | $65.70 |
|---|---|
| Data processing (100 GB × $0.045/GB) | $4.50 |
| Public IPv4 (2 × $0.005/hr × 730 hr) | $7.30 |
| NAT Gateway total | |
| Internet egress (100 GB × $0.09/GB), applies with or without NAT | $9.00 |
Nearest Fixedmark plan by bandwidth
Pro: $29/mo
200 GB, 500,000 requests, Dedicated IP pair, 1 region.
Planned launch pricing. Subject to change before general availability. Your platform's own egress charges still apply. All plans
When a NAT Gateway makes sense
A NAT Gateway gives a static outbound IP to compute inside your own AWS VPC: EC2, ECS, or Lambda attached to a VPC. If all your workloads live there, it is the native option.
It does not help apps on Vercel, Railway, Render, Netlify, or Supabase. Those need an outbound proxy with fixed IPs.
Compare in detail
Read the full AWS NAT Gateway vs Fixedmark comparison, the AWS Lambda static IP guide, or check your current IP with What's my IP.
Frequently asked questions
How much does an AWS NAT Gateway cost per month?
In us-east-1, one NAT Gateway costs $0.045 per hour, about $32.85 per month, plus $0.045 per GB processed and $0.005 per hour for its public IPv4 address. A highly available setup with one gateway in each of two AZs costs about $73 per month before any traffic.
Why is NAT Gateway data processing so expensive?
AWS charges $0.045 for every GB that passes through the gateway, on top of the normal $0.09 per GB internet egress charge. Heavy outbound traffic pays both.
Does internet egress apply with a proxy too?
Yes. Your cloud or platform charges for traffic leaving its network either way. This calculator shows egress separately so you can compare the NAT-specific costs.
Can I use a NAT Gateway for Vercel or Railway?
No. A NAT Gateway only works for compute inside your own AWS VPC, such as Lambda in a VPC, ECS, or EC2. Apps on Vercel, Railway, Netlify, or Supabase need a proxy for a static outbound IP.
Are these rates current?
The rates are AWS's published us-east-1 prices, checked in October 2026. Other regions cost more or less. Confirm current prices on the AWS pricing pages linked on this page.
Make it fixed.
Fixedmark is in early access. Join the list to get dedicated static IPs when your region opens.