VPC A ⟷ VPC Bįor three VPCs, this may be manageable, but as you begin to scale out your cloud environment this becomes complex and administratively burdensome.įigure 3 – Multiple direct peering relationships. The routing table in each VPC would also require updates to enable traffic flow. These VPC peering relationships would have to be stitched together one by one. The non-transitive nature is captured in the following example: VPC A ⟷ VPC Bįor VPC B and VPC C to communicate, direct peering must be established between the two, as shown in Figure 2.įigure 2 – To communicate with each other, VPC B and VPC C require direct peering. However, VPC B and VPC C cannot communicate with one another.
VPC A can communicate with VPC B and VPC C. To understand why, let’s examine the scenario in Figure 1.įigure 1 – In this scenario, VPC B and VPC C cannot communicate with each other. However, VPC peering’s non-transitive nature limits its use cases.
Prior to AWS Transit Gateway, VPC peering was used to enable the flow of traffic between VPCs. In this post, I will walk you through different network designs and make clear the advantages of using Megaport Cloud Router with AWS Transit Gateway as a way to route traffic across multiple AWS Regions. Megaport has earned the AWS Networking Competency and AWS Direct Connect Service Delivery designation, meaning we have been validated by AWS Partner Solutions Architects as experts in delivering specific AWS services for customers. Megaportis an AWS Advanced Technology Partner and global network as a service provider transforming the way businesses connect to the Amazon Web Services (AWS) Cloud. There’s another approach that can be effective when applied to multiple regions, and that’s using a virtual router service such as Megaport Cloud Router (MCR). Later, AWS Transit Gateway, akin to a virtual router, provided a more scalable, simpler networking solution within a given AWS Region.įor routing across multiple regions, peering could be applied to AWS Transit Gateways to enable traffic flow, and it requires static routes to be configured and maintained. VPC peering enabled instances in different VPCs to communicate with each other as if they were within the same network.
Routing traffic between virtual private clouds (VPCs) has seen several generations of evolution. By James Ronneberg, North America Partner Development Manager for Cloud at Megaport
0 kommentar(er)
