AWS Transit Gateway Pricing Calculator
Estimate attachment hours and per-GB data processing before hub-and-spoke networking becomes your fastest-growing bill.
- No signup
- Instant results
- ~2 min
Rates reviewed
Read the full breakdown — Amazon VPC Pricing covers billing dimensions, traps, and a 30-day cleanup plan.
Transit Gateway attachments
us-east-1list rates, pricing as of 2026-06-30. Inter-region peering attachments and multicast excluded. One TGW assumed. Source: AWS public pricing.
us-east-1: $0.05/hr per attachment ($36.50/mo) + $0.02/GB processed.
Who This Tool Is For
Network architects and FinOps leads sizing hub-and-spoke connectivity across multiple VPCs, accounts, or hybrid links.
Why We Built This Tool
Transit Gateway bills $0.05/hour per attachment plus $0.02/GB processed — attachment hours dominate at low traffic; data processing dominates at scale.
What Problem It Solves
- Attachment multiplication. Five VPCs = $182/month in hourly fees before a single gigabyte moves.
- Peering crossover. Below ~5–10 VPCs, full-mesh peering is often cheaper — TGW wins on operations at scale.
- Hidden inter-region. TGW peering data between regions bills the same $0.02/GB processing rate.
Read the VPC & TGW pricing guide or explore cloud cost optimization.
Frequently Asked Questions
Where do these Transit Gateway prices come from?
AWS published us-east-1 list prices (AWS VPC pricing), pricing as of 2026-06-30.
What counts as a billable attachment?
Each VPC, Site-to-Site VPN, Direct Connect, or TGW peering connection attached to a Transit Gateway incurs the $0.05/hour charge while active.
When does Transit Gateway pay off vs VPC Peering?
Peering has no hourly fee — only $0.01/GB each way for same-region traffic. TGW adds $36.50/month per attachment. Peering wins below ~5–10 VPCs needing connectivity; TGW wins on operational simplicity at scale.
Is the Transit Gateway itself billed hourly?
No separate TGW hourly fee — you pay per attachment and per GB processed. One TGW can serve many attachments.
How does TGW compare to NAT Gateway for egress?
NAT Gateway bills $0.045/hr + $0.045/GB per gateway. TGW is for inter-VPC routing, not internet egress — but teams sometimes compare total networking spend across both.
Does inter-AZ traffic through TGW cost extra?
TGW data processing is $0.02/GB regardless of AZ. Underlying ENI traffic may still incur standard inter-AZ transfer if endpoints are in different AZs.