Simplifying routing with MCR

Simplifying Routing Across Multiple AWS Regions with a Virtual Router Service

Learn about the advantages of using Megaport Cloud Router (MCR) to route traffic across multiple AWS Regions.

Routing traffic between virtual private clouds (VPCs) has seen several generations of evolution.

VPC peering enabled instances in different VPCs to communicate with each other as if they were within the same network.

Later, AWS Transit Gateway, akin to a virtual router, provided a more scalable, simpler networking solution within a given AWS Region.

For routing across multiple regions, peering could be applied to AWS Transit Gateways to enable traffic flow, but that requires static routes to be configured and maintained.

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).

Megaport is an AWS Advanced Technology Partner and global network as a service provider transforming the way businesses connect to the Amazon Web Services (AWS) Cloud.

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.

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.

. . .

Post is continued on the AWS Partner Network (APN) Blog.

James Ronneberg
Cloud Partner Development Manager