Transit Gateway Cost Calculator
Model Transit Gateway attachment-hour and per-GB charges, and compare against the peering mesh it replaces.
About Transit Gateway Cost Calculator
A Transit Gateway bills for every attachment for every hour it exists, plus a per-GB charge on traffic that crosses the gateway — and traffic between two attached VPCs crosses it once, not twice. The comparison worth making is against VPC peering, which has no hourly charge but needs n(n − 1) ÷ 2 connections because peering is not transitive, so the operational cost grows quadratically while the gateway grows linearly. The crossover point between a peering mesh and a Transit Gateway hub usually sits between five and ten VPCs, and knowing where it falls for your traffic profile prevents both a premature hub and an unmanageable mesh.
Formula
Transit Gateway Cost
cost = attachments × hours × attachment rate + GB processed × per-GB rate; a peering mesh of the same size needs n(n − 1) ÷ 2 links.
- attachments
- VPC, VPN, Direct Connect or peering attachments on the gateway
- attachment rate
- Hourly price per attachment for the region
- n
- Number of attached networks
Worked example
With the default values below, Transit Gateway Cost Calculator returns Estimated Monthly Cost of $319.00. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Transit Gateway attachmentsaccepts 1–5,000 attachments
- 6 attachments
- Price per attachment-houraccepts 0–2 USD
- 0.05 USD
- Data processed per monthminimum 0 GB
- 5,000 GB
- Price per GB processedaccepts 0–2 USD
- 0.02 USD
- Billable hours per monthaccepts 1–744 hours
- 730 hours
Results
- Estimated Monthly Cost
- $319.00
- Attachment Hour Charges
- $219.00
- Data Processing Charges
- $100.00
- Cost per Attachment
- $53.17
- Peering Links a Full Mesh Would Need
- 15
Step by step
- 1Values used
- 2Transit Gateway Cost
- 3Estimated Monthly Cost= 319.00
- 4Attachment Hour Charges= 219.00
- 5Data Processing Charges= 100.00
- 6Cost per Attachment= 53.17
- 7Peering Links a Full Mesh Would Need= 15
Assumptions and limits
- The result is derived only from the 5 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
How is Transit Gateway Cost calculated?
cost = attachments × hours × attachment rate + GB processed × per-GB rate; a peering mesh of the same size needs n(n − 1) ÷ 2 links. A Transit Gateway bills for every attachment for every hour it exists, plus a per-GB charge on traffic that crosses the gateway — and traffic between two attached VPCs crosses it once, not twice. The comparison worth making is against VPC peering, which has no hourly charge but needs n(n − 1) ÷ 2 connections because peering is not transitive, so the operational cost grows quadratically while the gateway grows linearly.
Why does Transit Gateway Cost matter?
The crossover point between a peering mesh and a Transit Gateway hub usually sits between five and ten VPCs, and knowing where it falls for your traffic profile prevents both a premature hub and an unmanageable mesh.
What values do I need to enter?
This calculator takes 5 inputs: Transit Gateway attachments, Price per attachment-hour, Data processed per month, Price per GB processed, Billable hours per month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Are these prices current?
The defaults are us-east-1 list prices for illustration only. Attachment and data processing rates vary by region, and cross-region peering attachments add their own transfer charge, so confirm the figures on the AWS Transit Gateway pricing page for your region.
Is data charged once or twice when it crosses a Transit Gateway?
Once. The data processing charge applies to data sent into the gateway from an attachment, so a VPC-to-VPC flow is billed a single time rather than on both the ingress and the egress attachment.