Direct answer
NAT Gateway charges by the hour and by the gigabyte, so traffic from private subnets to S3, image registries, and outside APIs adds up fast. Free S3 and DynamoDB gateway endpoints fix the most common cause.
Want someone to fix this for you? We'll match you with an AWS partner, at no cost.
Find my partner matchHow NAT Gateway is billed
AWS charges for each hour a NAT Gateway is configured and for each gigabyte it processes. In its US East (Ohio) example, both rates are $0.045. A regional NAT Gateway is charged for each Availability Zone it is configured in, so three AZs cost $0.135 per hour. Amazon VPC pricing Rates vary by region. Check yours before doing the math.
Worked example at US East (Ohio) rates
The hourly part is fixed. The per-GB part grows with your traffic, which is why the line keeps rising as you scale.
The five usual causes
The free fix: gateway endpoints
Gateway endpoints connect your VPC to S3 and DynamoDB without an internet gateway or NAT device, and AWS says there is no additional charge for using them. Once you associate a route table, every instance in those subnets uses the endpoint automatically. AWS gateway endpoints Note that the prefix lists are per region, so S3 traffic to another region still goes the old way.
How to find what is going through your NAT Gateway
- In Cost Explorer, group by usage type and look for NAT Gateway hours and bytes.
- Turn on VPC Flow Logs for the NAT Gateway's network interface.
- Sum bytes by destination. S3 ranges, registries, and log endpoints usually top the list.
- Fix the top destination first, then re-check the bill after a week.
Partner route
NAT Gateway is rarely the only leak.
If NAT Gateway is high, data transfer, logs, and idle environments usually are too. An AWS partner can give you partner pricing and use its DevOps team to fix all of it at no cost when your billing runs through it. Working with the right partner can reduce cloud costs by up to 40%.
No-cost initial review
A realistic route check should not cost the startup money. The partner is compensated by the provider or channel side when a qualified account moves forward. Paid implementation work is separate if it is not provider-funded.
Public form
Company age, website, AWS account, package rules, prior credits, Org ID.
Partner review
Run-rate, workload fit, migration plan, funded work, payment terms, retention case.
Cost to startup
The initial fit check should not cost money when there is a realistic provider opportunity.
Guardrail
No guaranteed credits, no fake Org ID, no partner shortcut without a real workload.
Related reading: why AWS partners offer free DevOps and running AWS without a DevOps engineer.
Recent field notes
What we are seeing from startup cloud-benefit reviews.
Based on 45 non-cancelled startup cloud-benefit calls booked since January 2026, the strongest-fit companies usually had one or more clear signals: existing cloud spend, credits ending soon, recent funding, AI or GPU-heavy workloads, or a planned infrastructure project.
These are internal patterns from recent startup conversations, not guaranteed provider approval criteria.
- 45
- non-cancelled calls
- 2026
- booked since January
- 5
- strong-fit signals
Free 60-second route check
Spending $1,000+ a month on AWS? We'll match you with the best partner for your situation, at no cost.
Answer 6 questions and you get:
- Your likely route: credits, extension, discount, funded work, migration support, or payment terms
- What evidence that route needs before anyone asks the provider
- The option to book a call about your case, or an email follow-up within 24 hours
Free. No commitment. Built for startups spending $1,000+ a month on cloud. Under that, the public programs above are usually the better route.