This article explains how to:
- Create a Hosted Connection in the Megaport Portal.
- Accept the Hosted Connection in the Amazon Web Services (AWS) console.
- Create a virtual interface (VIF) in the AWS console.
- Attach the VIF to a gateway in the AWS console.
A Hosted Connection is an AWS Direct Connect service that provisions connectivity on demand over pre-provisioned network circuits. A Hosted Connection with a capacity of 500 Mbps or less can support one private or public VIF. A Hosted Connection with a capacity of 1 Gbps or more can support one private, public, or transit VIF. You can obtain multiple VIFs by configuring multiple hosted connections. For more details, see Configure and maintain AWS Hosted Connections.
Unlike configuring a Hosted VIF, where the virtual interface and associated Layer 3 details are automatically provisioned, when you configure a Hosted Connection you must provision the virtual interface.
Before proceeding, ensure that you have already configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations. The AWS documentation provides detailed steps for VPC configuration as well as how to create and deploy different gateway types.
Creating an AWS Hosted Connection
To create an AWS Hosted Connection, you need your AWS Account number and the details of the VPC environment.
To create a Hosted Connection
- In the Megaport Portal, complete steps 1 through 10 in Configure and maintain AWS Hosted Connections.
The deployment can take several minutes.
After creating a Hosted Connection, it is activated after you accept it in the AWS console.
To accept a Hosted Connection
- In AWS, go to Services > AWS Direct Connect > Connections and click the connection name.
- Click Accept.
The State will be pending for a few minutes while AWS deploys the connection. After it is deployed, the State changes from “ordering” to “available”.
The connection is now available and ready to use; however, a VIF is required to connect to AWS services.
Creating a virtual interface
Next, you’ll create a VIF and attach this Hosted Connection to a gateway.
To create and attach a VIF
- In the AWS console, click Create virtual interface.
- Select the interface type. The type will vary depending on the type of service you need to access.
- Private – Access resources running into a VPC using their private IP addresses. You can choose to terminate a private virtual interface on a private virtual gateway (to access a single VPC) or to a Direct Connect gateway (this will give you a 1 VIF to 10 VPCs mapping).
- Public – Access all AWS public endpoints, as well as all AWS resources that are reachable by a public IP address.
- Transit – Transport traffic from a Direct Connect gateway to one or more transit gateways. A transit virtual interface is available only on a Hosted Connection with a capacity of at least 1 Gbps. Slower connections are filtered out and no longer appear in the interface.
- Specify the configuration details:
- Virtual interface name – Enter a name for the virtual interface.
- Connection – The physical connection where you want this virtual interface to be provisioned. The name you provided for the Hosted Connection in the Megaport portal appears here.
- Virtual interface owner – The account that will own the virtual interface. Select My AWS account.
- Direct Connect gateway – Select the Direct Connect gateway to attach this virtual interface to. A transit VIF is not directly attached to a Transit gateway, but to a Direct Connect gateway.
- VLAN – The VLAN assigned to the virtual interface. Leave this value as is.
VLANs cannot be extended from on-premises to AWS, and are used only for traffic separation between different virtual interfaces.
- BGP ASN – Enter the Border Gateway Protocol (BGP) autonomous system number (ASN) for the on-premises side of the BGP session.
The following BGP details can be filled out or left blank. When left blank, they are auto-populated by AWS.
You can also choose whether you want the virtual interface to support Jumbo frames. Enable Jumbo MTU to support an Ethernet packet of 8500 bytes.
- Click Create virtual interface.
To view the VIF details and state, navigate to Services > AWS Direct Connect > Connections > Name of the Megaport-Created-Hosted Connection.
If BGP hasn’t been configured, the interface State will be shown as “down”.
The last step is to configure BGP on the on-premises network device. The AWS documentation provides details on how to download the router configuration as a unique feature of Hosted Connections. If you have a Megaport Cloud Router (MCR) instead of an on-premises device, see Creating Connections to AWS Direct Connect.
Note: If you download the router configuration files, verify that the AWS and Megaport VXC VLAN numbers match. While in most cases Megaport uses the same VLAN number as AWS, the VLAN might be different in the Megaport configuration that is connected to your on-premises device given the automation of the platform.