Explain AWS VPC peering vs Transit Gateway — when to use each?

VPC Peering — direct 1:1 connection between two VPCs. Non-transitive (A→B and A→C does NOT enable B→C). Cheap, simple. Use for small hub-and-spoke or 2-3 VPC integrations. Transit Gateway — central hub for many VPCs (up to 5,000) and on-prem connections. Transitive routing. More expensive but scales massively. Use for: enterprise multi-account architectures, multi-region replication, hybrid cloud connectivity. Senior network engineer roles in Bangalore now ask AWS networking depth — TGW is common interview topic.

Want the full explanation? This is the atomic answer suitable for quick interview prep. For the structured deep-dive — including code samples, strong-answer vs weak-answer notes, common follow-up questions, and how this fits the larger cisco / network engineer topic — see the full Q&A on Networkers Home:

→ Cisco / Network Engineer Interview Hub — Full Q&A with deep context

How Networkers Home prepares students for this kind of question

This question reflects real interview rounds at Bangalore's top enterprise networking and infrastructure teams. Networkers Home's flagship courses include mock interview sessions drilling exactly these question patterns, with feedback from interviewers who have hired for the role.

→ View the complete cisco / network engineer interview prep hub
→ View the related Networkers Home course
→ Book a free career consultation

Explain AWS VPC peering vs Transit Gateway — when to use each?

How Networkers Home prepares students for this kind of question

Related Cloud Networking questions

Q. What's the difference between AWS Network Load Balancer (NLB) and Application Load Balancer (ALB)?