AWS Interconnect from Megaport is in Preview. Features, supported locations, and connection speeds are limited during the Preview and are subject to change. For more information, see Preview release.
- Builds redundancy into the product — Every AWS Interconnect is delivered over diverse paths, providing a highly resilient connection.
- One AWS connection to manage — The routing infrastructure underneath is provisioned, monitored, and maintained by Megaport.
- Supports ordering from either side — You can start the order in the AWS console or in the Megaport Portal.
- Connects to your existing network — Any Port, MCR, MVE, or NAT Gateway in the same metro can reach the AWS Interconnect through a private VXC. For more information, see Creating a Private VXC.
Preview release
AWS Interconnect is available as a Preview release. These conditions apply during the Preview:- Locations — AWS Interconnect is available in a limited set of metros. Ashburn and San Jose are available during the Preview.
- Speed — All AWS Interconnects are 1 Gbps. You cannot change the speed of an AWS Interconnect after you order it.
- Connections — You can attach up to 25 VXCs to an AWS Interconnect.
- Service lifetime — Preview AWS Interconnects are not carried over to the general release. You need to reorder for production use. Do not use a Preview AWS Interconnect for production traffic.
How it works
To order an AWS Interconnect, you choose a metro, a connection speed, and an , and you provide your AWS account ID. You receive a single diverse service in return. The Megaport and AWS networks exchange the connection parameters machine-to-machine and agree on them without your involvement. An AWS Interconnect operates at . It is a routed service, not a Layer 2 circuit, so traffic between your network and your is forwarded using BGP routes rather than a VLAN you manage. The ordering process involves these steps:- You order an AWS Interconnect in the Megaport Portal, or you start the order in the AWS console and bring the activation key to the Megaport Portal.
- Megaport builds the routing infrastructure for the AWS Interconnect and connects it to the AWS ports in that metro.
- If you started the order in the Megaport Portal, generate an activation key for the AWS Interconnect when it is ready, and submit the key in the AWS console under the AWS account ID you provided. The key expires if it is not submitted in time.
- Megaport and AWS coordinate the VLANs, IP subnets, MTU, and BGP sessions for each path.
- You order a VXC from an existing service (such as a Port, MCR, MVE, or NAT Gateway) to the AWS Interconnect.
- Traffic flows between your network and the AWS region over the coordinated BGP sessions.
Resiliency
AWS Interconnect is designed for high resilience, with protection at both the physical layer and the routing layer. At the physical layer, Megaport delivers every AWS Interconnect over multiple link aggregation groups (LAGs), spread across separate locations in the metro, and across diversity zones within each location. At the routing layer, AWS Interconnect links its routers so that they share routes, and traffic continues over the remaining LAGs if any LAG goes down. These layers of redundancy work together, so an AWS Interconnect stays connected even if an entire location or diversity zone becomes unavailable. When you order a VXC to an AWS Interconnect, the diversity zone of the A-End determines which router the VXC lands on. A connection in the Red zone lands on a Red-zone router, and a connection in the Blue zone lands on a Blue-zone router. For more information about diversity zones, see MCR Diversity.Difference between AWS Interconnect and AWS Direct Connect connections
Megaport offers two different ways to connect to AWS. AWS Interconnect is a separate product from the AWS Direct Connect models described in Connecting to AWS Direct Connect. A key difference is who configures the connection. With AWS Direct Connect connections, you order a VXC to AWS and then configure the BGP session yourself. With AWS Interconnect, Megaport coordinates the configuration with AWS on your behalf.
Use AWS Interconnect when you want Megaport to manage the routed connection to AWS for you. Use a Direct Connect model when you need a connection type that AWS Interconnect does not offer, or when you want to control the BGP and VLAN configuration yourself.
For more information about the Direct Connect models, see Connecting to AWS Direct Connect.