AWS — Difference between VPC Peering and Transit Gateway

<p>Comparisons: AWS VPC Peering vs AWS Transit Gateway in AWS</p> <h1>TL;DR:</h1> <p>VPC Peering and Transit Gateway are used to connect multiple VPCs. VPC Peering provides Full-mesh architecture while Transit Gateway provides hub-and-spoke architecture. Transit Gateway gives VPC connectivity at scale and simplifies VPC-to-VPC communication management over VPC Peering with a large number of VPCs.</p> <h1>VPC Peering</h1> <p><a href="https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html" rel="noopener ugc nofollow" target="_blank">AWS VPC Peering</a>&nbsp;connection is a networking connection between two VPCs that enables you to route traffic between them privately. Instances in either VPC can communicate with each other as if they are within the same network.</p> <p><img alt="" src="https://miro.medium.com/v2/resize:fit:700/1*Abu4eeFODEkdG7hXwvb5dg.png" style="height:595px; width:700px" /></p> <p>Awesome Cloud &mdash; AWS VPC Peering</p> <h2>Advantages of VPC peering</h2> <ul> <li>Low cost since you need to pay only for data transfer.</li> <li>No bandwidth limit.</li> </ul> <h2>Disadvantages of VPC peering</h2> <ul> <li>Complex at scale. Each new VPC increases the complexity of the network. Harder to maintain route tables compared to TGW.</li> <li>No transit routing.</li> <li>Maximum 125 peering connections per VPC.</li> </ul> <p><a href="https://medium.com/awesome-cloud/aws-difference-between-vpc-peering-and-transit-gateway-comparison-aws-vpc-peering-vs-aws-transit-gateway-3640a464be2d"><strong>Click Here</strong></a></p>