Configuring and Maintaining AWS Hosted VIFs
To deploy an AWS Hosted VIF, you need your AWS Account number and the details of the VPC environment.
You can deploy multiple VXCs to the same VPC (for redundancy); however, you cannot deploy a single VXC to multiple VPCs. You need a separate VXC to connect to each AWS VPC.
Watch a 16-minute video for the Hosted VIF setup process.
To create a Hosted VIF connection
- In the Megaport Portal, go to the Services page and select the Port you want to use.
If you haven’t already created a Port, see Creating a Port.
Add an AWS connection for the Port.
If this is the first connection for the Port, click the AWS tile. The tile is a shortcut to the configuration page. Alternatively, click +Connection, click Cloud, and click AWS.
For Provider click AWS and for AWS Connection Type click Hosted VIF.
In the Select Destination Port list, select the AWS region and the interconnection point for your connection and click Next.
You can use the Country filter to narrow the selection.
Specify these connection details:
- Name your connection – The name of your VXC to be shown in the Megaport Portal. (Tip – match this to the VXC name on the next screen for easy mapping.)
- Invoice Reference – This is an optional field. It can be any text, such as a PO number or billing reference number.
- Rate Limit – This is the speed of your connection in Mbps. Accepted values range from 1 Mbps to 5 Gbps in 1 Mbps increments. Note the sum of all hosted virtual VXCs to a service can exceed the Port capacity (1 or 10 Gpbs) but the total aggregate will never burst beyond the Port capacity.
Preferred A-End VLAN – Optionally, specify an unused VLAN ID for this connection. This must be a unique VLAN ID on this Port and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport will assign one.
Alternatively, you can click Untag to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port. (The VLAN for the AWS side termination will be automatically allocated and will not impact your Megaport details.)
Specify the cloud details.
Select Public or Private.
Private – Access private AWS services such as a VPC, EC2 instances, load balancers, RDS DB instances, on private IP address space.
Public – Access public AWS services such as Amazon Simple Storage Service (S3), DynamoDB, CloudFront, and Glacier. You’ll also receive Amazon’s global IP prefixes (approximately 2,000 prefixes).
Public VIFs require manual intervention from Amazon and could take up to 48 hours. For details, see Configuring Public AWS Connections with IP Addresses Provided by AWS.
AWS Connection Name – This is a text field and will be the name of your virtual interface that appears in the AWS console. For easy mapping, use the same name for this field as you did for the VXC name on the previous screen.
AWS Account ID – This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
Customer ASN – Your networks Autonomous System Number. For Private Direct Connects, this must be a private ASN and the supported private ASN range is 64512 - 65535. For public Direct Connects, this can be either a private or public ASN. If using a Public, you must own the public ASN.
BGP Auth Key – Optional field allowing you to specify the BGP MD5 key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. (The key is not displayed in the AWS console.)
Customer IP Address – The IP Address space (in CIDR format) you will use on your network for peering. For private connections, this field is optional and if left blank, Megaport assigns a private /30 address. For public connections, this field is required and needs public IPs (/30) allocated by you for BGP connectivity. You must own the public IPs.
Amazon IP Address – The IP address space in CIDR format assigned in the AWS VPC network for peering. For private connections, this field is optional and if left blank, Megaport automatically assigns a private /30 address. For public connections, this field is required and needs public IPs (/30) allocated by you for BGP connectivity. You must own the public IPs.
Prefixes – For Public connections only - IP Prefixes to announce to AWS. RIR-assigned IPv4 addresses only. Specify the prefixes you will advertise when deploying a Public Direct Connect.
Once you configure Prefixes for a Public connection, you cannot change them and the field is dimmed. To change this value, create a support ticket with AWS so they can make this change a non-impacting way. Or you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.
A summary page appears that includes the monthly cost. Click Back to make changes or click Add VXC to move this configuration to your cart. Once you have finished this configuration, you can configure additional VXCs or proceed through the checkout process.
Click Order and complete the ordering process to deploy the VXC.
Megaport will deploy the connection. The deployment can take several minutes.
- Accept the virtual interface in AWS.
To review and accept in the AWS console, go to Services > AWS Direct Connect for the Direct Connect dashboard. For a private virtual interface, you must also have an existing virtual private gateway or Direct Connect gateway. For details, see the AWS documentation.
Once you accept the hosted VIF in AWS, the VXC state changes to configured in the Megaport Portal. You can review the configuration details to get the A-End VLAN ID, BGP Auth Key, and IP addresses that you need to configure your router.
To edit a Hosted Virtual Interface
Click the gear icon next to the connection in the Megaport Portal to make changes.
If you have permissions to edit VXCs, you can modify the details on the Megaport side including the connection name, VLAN ID, invoice reference, and rate limit. Once submitted, those changes take effect in a few minutes.
You can also make changes to the AWS details of a VXC. When you change the AWS details, the service will be rebuilt and you need to accept changes to the connection in AWS.
To delete a Hosted Virtual Interface
- Click the trash can icon next to the connection in the Megaport
Portal to delete.