CloudConsole

Transit Gateway vs VPC peering

Updated 17 November 2026 · How we write and check guides

Short answer

Use VPC peering for a few VPCs that need to talk directly: there is no hourly charge, data within an AZ is free and performance is the best available. Use Transit Gateway once you have roughly ten or more VPCs, need shared VPN or Direct Connect access, or want central route tables for segmentation; you pay per attachment-hour and per GB processed for that simplicity.

Transit Gateway vs VPC peering: deciding factors Topology, Transitive routing, On-premises access, Cost; When peering is…
The deciding factors from this page's comparison table, and the cases where each option wins.

Transit Gateway vs VPC peering

FactorVPC peeringTransit Gateway
TopologyPoint-to-point; a full mesh grows as n(n-1)/2Hub and spoke; each VPC attaches once
Transitive routingNot supportedSupported, controlled by TGW route tables
On-premises accessEach VPC needs its own VPN or Direct ConnectAttach VPN and Direct Connect once, share with all VPCs
CostNo charge to create; data transfer within an AZ free, cross-AZ and inter-Region chargedPer attachment-hour plus per GB processed, plus data transfer
ScaleUp to 125 active peerings per VPCThousands of VPCs per Regional gateway
Cross-RegionInter-Region peeringTGW inter-Region peering
Overlapping CIDRsNot allowedNot routable between overlapping ranges

When peering is the better choice

  • Two to a handful of VPCs, such as an app VPC and a shared-services VPC.
  • High-volume traffic between two VPCs, where Transit Gateway's per-GB processing would add up.
  • Latency-sensitive paths: peering adds no extra hop.

AWS guidance is that peering suits fewer than about ten VPCs that you can manage connection by connection, and offers the lowest overall cost and highest aggregate performance of the inter-VPC options.

When Transit Gateway is the better choice

  • Many VPCs across accounts in an AWS Organization, shared through AWS RAM from a network account.
  • Central hybrid connectivity: one set of VPN or Direct Connect attachments for everything.
  • Segmentation: separate route tables for production, non-production and shared services.
  • Central inspection: routing traffic through a security VPC with AWS Network Firewall or appliances.

Using both and migrating

Mixing is normal. Keep peering for one or two heavy VPC pairs and attach everything else to Transit Gateway. When migrating a mesh to Transit Gateway, attach VPCs first, add TGW routes alongside the peering routes, then remove peering routes one VPC pair at a time. The most specific route wins, so a peering route for the exact CIDR keeps taking traffic until you delete it.

Check alternatives as well: AWS PrivateLink exposes a single service across VPCs without any routing, and VPC sharing lets several accounts use subnets in one VPC with no connection at all.

Common wrong reasons

  • "Transit Gateway is always more secure." Both keep traffic private on AWS. Security comes from route tables, security groups and NACLs either way.
  • "Peering is free." Creating it is; cross-AZ and inter-Region data transfer over it is charged.
  • "We will need TGW eventually, so start now." With three VPCs you pay attachment and processing charges for routing you do not need yet.

Questions

Is Transit Gateway more expensive than VPC peering?

Usually yes for the same traffic, because Transit Gateway charges per attachment-hour and per GB processed while peering has no hourly charge. It saves operational effort at larger scale.

Does VPC peering support transitive routing?

No. If A peers with B and A peers with C, B cannot reach C through A. You need a direct B to C peering or a Transit Gateway.

How many VPC peering connections can a VPC have?

Up to 125 active peering connections per VPC, according to AWS networking guidance.

When this happens away from your desk

Routing mistakes show up as connection timeouts between services that worked yesterday, usually right after a route table change. CloudConsole is being built to show alarms alongside recent changes on a phone with production guardrails.

About the app → · Download on the App Store

Sources