AWS Direct Connect

You can create a network connection from your Megaport physical port to AWS with Virtual Cross Connections (VXCs) and AWS Direct Connect. 

Megaport supports three AWS Direct Connect models: 


Hosted Virtual Interfaces (Hosted VIFs)

Hosted VIFs can connect to public or private AWS cloud services. Each VXC (Hosted VIF) lets you manage the bandwidth and as long as the total bandwidth of the VXCs does not exceed the size of the Megaport, utilization of each VXC (to the VPC) will not impact the other VPCs. 

Key features include:

  • Connections can share bandwidth, which is managed and monitored to ensure defined network performance. 
  • If you connect to AWS from a Megaport Cloud Router (MCR), the Hosted VIF provides access to the routing information for automatic configuration of your MCR. 
  • You can change the service speed without impact to the service.
  • This model does not support Transit Gateway virtual interfaces.
  • AWS Direct Connect port charges are included with your Megaport order. You are informed of the billing details and shown the Megaport rates as you configure the connection. 
  • Maximum VXC speed of 5 Gbps 

Note: This is the original portal option supported by Megaport for AWS Direct Connect. 

To get started with Hosted VIFs:


Hosted Connections

A Hosted Connection with a capacity of 500 Mbps or less can support one private or public virtual interface. A Hosted Connection with a capacity of 1 Gbps or more can support one private, public, or transit virtual interface. Key features include:

  • Support for Transit Gateway for connections at 1 Gbps and higher.
  • Dedicated (not shared) bandwidth with one-to-one subscription.
  • You cannot change the service speed after you create the connection. To change the speed, you must create and configure a new connection.
  • The configuration process does not have automatic access to routing information for the Megaport Cloud Router and you need to configure the routing manually.
  • Maximum VXC speed of 10 Gbps.
  • Support for diverse AWS ports for resiliency and to avoid any single-point-of-failure.  
  • AWS Direct Connect port charges are billed by Amazon. 

With Hosted Connections, you can aggregate connections using Transit Gateway and have a single Hosted Connection with dedicated bandwidth instead of multiple Hosted VIFs sharing the bandwidth. With this scenario, a VPC can be impacted by other VPCs requiring bandwidth over the same connection.

Note:  If you are not co-located in a data center that offers Hosted Connections, you can use a VXC to connect to the closest enabled location.

To get started with Hosted Connections:


Direct Connect dedicated connection

A Direct Connect dedicated connection can support up to 50 public or private virtual interfaces and one transit virtual interface. With this option, you provision a Direct Connect port in the AWS Console and work with Megaport to set up a physical cross connect from the Direct Connect port to a Megaport at the same data center. Then, using a private VXC, you can connect the Megaport to a second Megaport in a different data center. 

Key features include:

  • You can change the service speed without impact to the service.
  • Support for a large number of VPCs.
  • Support for Transit Gateway configurations.
  • AWS port changes are billed by Amazon. 

To get started with a Direct Connect dedicated connection:


Configure and maintain AWS Hosted VIFs

To deploy an AWS Hosted VIF, you need your AWS Account ID and the details of the VPC environment.

Note: 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 video for the Hosted VIF set up process. 

To create a Hosted VIF connection

  1. In the Megaport portal, go to the Services page and select the port you want to use.
    If you haven’t already created a Megaport, see this KB article.
  2. 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.

  3. For Provider, click AWS and for AWS Connection Type, click Hosted VIF.

  4. 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.
  5. 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. 
    • 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 4090. If you specify a VLAN ID that is already in use, Megaport will assign the next closest available value. If you don’t specify a value, Megaport will assign one.
      Alternatively, you can click to Untag for this VXC 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.)
  6. Click Next
  7. 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.Specify the cloud details.
      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). Note: Public VIFs require manual intervention from Amazon and could take up to 48 hours.
    • 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.

  8.  Click Next.
    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.
  9. Click Order and complete the ordering process to deploy the VXC.
    Megaport will deploy the connection. The deployment can take several minutes.  
  10. 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.


Configure and maintain AWS Hosted Connections

Each Hosted Connection supports a single VIF and you can obtain multiple VIFs by configuring multiple hosted connections. 

Hosted Connections support diverse connections. Diverse connections improve the robustness of your network by using different physical infrastructure to provide network services. They build in redundancy and eliminate single points of failure.  You can achieve diversity by connecting to AWS ports in different diversity zones. Each destination port has either an orange or blue icon to indicate the diversity zone. 

To create diverse connections, you need to create two connections: one connection for each diversity zone. 

To deploy an AWS Hosted Connection, you need your AWS Account ID and the details of the VPC environment.

To create a Hosted Connection

  1. In the Megaport portal (portal.megaport.com), go to the Services page and select the port you want to use.
    If you haven’t already created a port, see this KB article
  2. 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.

  3. For AWS Connection Type, click Hosted Connection.

  4. In the Select Destination Port list, select the AWS region and the interconnection point for your connection and click Next.
    Each destination port has either a blue or an orange icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
    You can use the Country filter to narrow the selection and you can filter by diversity zone.

  5. Specify these connection details:
    • Name your connection – The name of your VXC to be shown in the Megaport Portal. 
    • 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. The speed cannot be changed once deployed. The drop-down list shows predefined rate limits available for your port, up to 10 Gbps. (Note: Transit Gateway is available only for speeds at 1 Gbps or above.)

  6. Click Next
  7. Specify the cloud details. 
    • 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, the field defaults to the same name you specified 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.

  8. Click Next.
    A summary page appears that includes the monthly cost. 
  9. 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. 
  10. Click Order and complete the ordering process to deploy the VXC.
    Megaport will deploy the connection. The deployment can take several minutes. 
  11. In AWS, accept the connection and create a VIF.
    To review and accept in the AWS console, go to Services > AWS Direct Connect > Connections and click the connection name to review the details and accept. See Creating a Public, Private, or Transit Virtual Interface on a Hosted Connection for details on accepting the connection and creating a VIF.

To edit a Hosted Connection 

  • Click the gear icon next to the connection in the Megaport Portal to make changes.

    You cannot change the rate limit or the AWS connection name or account ID for Hosted Connections.
    You can modify the details on the Megaport side including the connection name, VLAN ID, and invoice reference. Once submitted, those changes take effect in a few minutes. 

To delete a Hosted Connection

  1. In AWS, open the AWS Direct Connect console.
  2. Delete the virtual interface and then delete the connection.
    You can only delete a connection if there are no virtual interfaces attached to it. 
  3. In the Megaport portal, click the trash icon next to the VXC and confirm the deletion when prompted.

    Until you delete the virtual interface and connection in the AWS console, you cannot delete the VXC in the Megaport portal.

Configure a Direct Connect dedicated connection

A Direct Connect dedicated connection can support up to 50 public or private virtual interfaces and one transit virtual interface. The configuration requires a physical cross connect between a Megaport and a Direct Connect port and a virtual cross connect between the Megaport connected to the Direct Connect port and a second Megaport.  

To create a Direct Connect dedicated connection

  1. Provision a Direct Connect port in the AWS Console and designate Megaport as the vendor. 
  2. Download a LOA from AWS.
  3. Provision a Megaport in the same data center as the Direct Connect port. 
  4. Contact your Megaport account manager to set up a physical cross connect from the Direct Connect port to the Megaport. 
  5. Configure a private VXC to connect the Megaport attached to the Direct Connect port to a second Megaport in a different data center. 

This connection is not set up exclusively through the Megaport portal, but instead requires direct coordination with Megaport sales and support. 

Helpful References Outside of the Knowledgebase

To learn more about AWS Direct Connect models and features, explore these resources.

Additional Megaport Information

Amazon Documentation

©2020 Megaport. Megaport, Virtual Cross Connect, VXC and MegaIX are registered trademarks of Megaport (Services) Pty Ltd ACN 607 432 646.

Log in with your credentials

Forgot your details?