AWS VPC peering vs Transit Gateway
The following is the some of the main differences between AWS VPC peering and Transit Gateway:
Aspect |
VPC Peering |
Transist Gateway |
---|---|---|
Scope |
It Connects the VPCs withing the same AWS region. |
It connects with multiple VPCs and On-premises networks across AWS regions. |
Topology |
It establish point to point connections between individual VPCs. |
It performs Hub and Spoke architecture with centrailized routing. |
Communication |
It establishes direct communication between the peered VPCs. |
It performs centralized routing for inter-VPC and VPC-to-on-premises communication. |
Scaling |
Limited scaling, manual configuration is performed for each peering connection. |
Highly scalable, supporting is provided for thousands of VPCs. |
Transtivity |
Not Transitive, Each VPC must establish seperate peering connections. |
Transitive Routing, simplifying connectivity between mulitple VPCs. |
Cost |
data transfer costs between peered VPCs. |
Transit gateway and data processing Charges apply on this. |
Amazon VPC – Concept of VPC Peering
Amazon peering provides an effective way of linking Virtual Private Clouds ( VPCs ) and offers strong networking capabilities inside AWS. In this Article, the complexities of VPC peering are addressed with an effective way of explanation. This Article clarifies how to establish smooth communication across different cloud environments in AWS.