Skip to content

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.

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.

To create a Hosted VIF connection

  1. In the Megaport ONE Portal, choose Networking > Services.
  2. Select the Port you want to use.
    If you haven’t already created a Port, see Creating a Port.
  3. Click Actions and choose Add Connection.
    Add Connection
  4. Specify the General details:
    • Connection Type – Choose Cloud Virtual Cross Connect.
    • Cloud Provider – Choose Amazon Web Services.
    • AWS Connection Type – Choose Hosted VIF.
      AWS new connection details
  5. Select the AWS destination port.
    You can search for your preferred AWS port using the Region drop-down list, or enter a search term to filter results as you type. Click Clear Filters to reset the filters. AWS new connection details

  6. Specify the AWS cloud configuration details:

    • AWS Connection Name – This 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 in the previous section.
    • 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.
    • Type – 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 will also receive Amazon’s global IP prefixes (approximately 2,000 prefixes).

      Note

      Public VIFs require manual intervention from Amazon and could take up to 72 hours. For details, see Configuring Public AWS Connections with IP Addresses Provided by AWS.

    • 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 Password – Optional field allowing you to specify the BGP MD5 key. If you leave this blank, Megaport ONE negotiates a key automatically for you with AWS which will be displayed in the Megaport ONE Portal. (The key is not displayed in the AWS console.)

    • Customer IP Address – The IP Address space (in CIDR format) that you will use on your network for peering. For private connections, this field is optional and if left blank, Megaport ONE 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 ONE 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.

    • Amazon Prefixes – 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.

    AWS new Hosted VIF configuration details

  7. Specify the VXC Configuration details:

    • VXC Name – The name of your VXC to be shown in the Megaport ONE Portal. (Tip – match this to the AWS Connection Name in the next section for easy mapping.)
    • 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 Gbps, or 100 Gbps in some locations) 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 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 ONE will assign one.

      Alternatively, you can click Untag VLAN 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 ONE details.)
      AWS new connection details

    The monthly price updates dynamically based on your selections. (Note that some partner managed (client) accounts do not display the pricing details).

  8. Specify the Billing Details:

    • Service Level Reference (Optional) – Specify a unique identifying number for the VXC to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.

      Note

      Partner-managed accounts can apply a Partner Deal to a service.

    • Promo Code – If you have a promo code, enter it and click Add Code.
      AWS details for Hosted VIF connection

  9. Click Create Connection to deploy the VXC.

  10. Review the connection details and click Confirm to deploy the connection. The deployment can take several minutes.
    Once you have finished this configuration, you can configure additional VXCs.
  11. 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 ONE Portal. You can review the configuration details to get the A-End VLAN ID, BGP password, and IP addresses that you need to configure your router.

To edit a Hosted Virtual Interface

  1. Click the Gear icon Gear icon next to the connection in the Megaport ONE Portal.
  2. Choose Edit.
    Edit a Hosted VIF

    If you have permissions to edit VXCs, you can modify the details on the Megaport ONE side including the connection name, VLAN ID, Service Level Reference, and VXC rate limit. Once saved, 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

  1. Click the Gear icon Gear icon next to the connection in the Megaport ONE Portal.
  2. Choose Delete.
    Delete icon  
  3. Type DELETE to confirm, and then click Delete.

Last update: 2023-01-21