Note: Using a Direct Connect to connect directly to a Virtual Private Gateway (VGW) is no longer recommended by AWS. Instead Amazon recommends that you should use the Direct Connect Gateway  for flexibility to connect multiple VPCs across regions and support for added future functionality. This procedure is included for legacy reasons only.


To connect to AWS, you must have:

  • A Pureport Account with permissions to create Networks and Connections
  • An AWS Virtual Private Gateway and Direct Connect Gateway configured with the Amazon Default ASN attached to an AWS VPC
  • Access to your AWS Account(s) via the AWS Console.
    Note: If you are using an IAM account or Role, ensure you have the necessary permissions granted.

Log into AWS Console and find your AWS Account ID

To locate your AWS Account ID, access AWS Management Console Support Center (

Your Account number is locate at the top of the page:

Create an AWS DirectConnect connection in the Pureport Console

To create a new connection:

  1. Login to the Pureport Console using an account with an appropriate Role.
    At a minimum you will need the Create and Update permissions for Networks. For more information on Roles, see the Accounts, Members and Roles article.

  2. In the left navigation bar, select the Networks tab.
  3. On the Networks screen, select the network to add the connection to AWS.
    Note: To create a new network for this connection, see the Creating a Network article.

  4. Select Add Connection... at the top-right of the console, or click a location on the network map.

  5. In the Type drop-down list, select AWS Direct Connect as the connection type, then click Next.

  6. Next, select the Pureport location you want to connect from:
  7. Select the AWS region you would want to connect to, and click Next. Note that only AWS Regions that are directly accessible from the Pureport POP you selected are available.
    Be aware that if you want to connect to an AWS Region that is not close to the Pureport POP you want to use, you should consider connecting to a Direct Connect Gateway instead of directly to a VGW. Connecting to a Direct Connect Gateway allows you to connect from any Pureport POP to any AWS Region, and connecting to Regions in the same geopolitical region (eg: North America) can be done at no additional cost with the Direct Connect Gateway.
  8. Select a Peering Type. For VPC Connectivity via a VGW, choose Private. Refer to the article on Creating an AWS Public VIF for more info on the Public option.

  9. Select the Speed & Availability of the connection. Note that Pureport's connection SLAs only apply to when HA is selected.

  10. Enter your AWS Account ID, and click Next.
  11. In the BGP Ssettings section, enter the default ASN (autonomous system number) used by AWS, 64512 then click Next.
    Note: If you used a custom ASN when you created the VGW in the AWS Console, you will need to enter the value you used here.

  12. Optionally add any CIDR networks you may be connecting. Note, these are only used when subsequently connecting a policy-based VPN to your Pureport network and are completely optional. Click Next when finished.

  13. You may also enable and configure Cloud Grade NAT if desired, as detailed in the Cloud Grade NAT knowledge-base article. Then click Next.

  14. Enter a meaningful Name and Description, then click Add Connection.

  15. After saving the Connection, the system displays the Primary and Secondary Gateway information:connection.

  16. Record the following information from the Primary and Secondary Gateways in the new connection (you can use the copy icon to the right of each item to ensure an exact copy to the clipboard):
    • Pureport IP
    • Pureport ASN
    • Remote IP
    • BGP Password

You will need this information later.

Accept the Hosted Connection in the AWS Console

After creating the new Connection, use this procedure to accept the Connection in the AWS Console. See "Accepting a Hosted Connection" in the AWS Direct Connect User Guide for details.

  1. In the Purport Console, you will be presented with a Post-Configuration screen with details about the connection next steps once the connection to AWS has been provisioned.

  2. To create Accept each of the connections, Click on the "Via the AWS Console" drop box (Via the AWS CLI can also be used if you are leveraging the CLI to manage your cloud environment.  This option will produce the CLI command to accept each of the provisioned connections).

  3. Click on each of the Blue boxes, a new window will open to AWS directly to the associated connection with all values pre-populated.  Simply click accept in the AWS screen to accept the connection and close the new window.

  4. Repeat steps 2 & 3 to accept the second connection.  Optionally, if you do not wish to leverage the links through the Pureport console, the following steps can be taken via the AWS console to complete the acceptance.
  5. Click Next to start creating the Virtual Interface.

Note:  The following steps are only needed if not using the Connection Acceptance steps via the Pureport console as mentioned above.

  1. Open the AWS Direct Connect console at
    If necessary, change the Region in the navigation bar.

  2. In the navigation pane, choose Connections.

  3. On the Connections page are the two connections you created: Primary and Secondary. These connections are named the same as the connections you created in the Pureport Console. Both in the ordering state.
    Note: If you are not using an HA connection, there is only a Primary connection.

  4. Select the Primary hosted connection and choose Accept.
  5. Select Confirm in the confirmation window.

Repeat steps 4 and 5 for the Secondary connection.

Create a Private Virtual Interface

  1. Now that the connections have been created, you will be presented with the steps to create your Virtual Interfaces for your new connections.
  2. You will be presented with an option to create your connection using a Direct Connect Gateway (AWS best practice) or via a Virtual Private Gateway.  Simply select the radio button of your choice and enter in the associated AWS Virtual Private Gateway ID.
  3. Expand the "Via the AWS Console" drop down box and click on each of the buttons to create your Virtual Interface. This will open a new window with the AWS console pre-populated with the necessary settings to create your virtual interface.
  4. Review the settings in the AWS console and click "create virtual interface".  You may need to scroll to the top of the AWS console for a successful creation notice.

    Note:  It can take up to five minutes for the connection acceptance to process in AWS.  If you receive an error at this point, ensure that enough time has elapsed for the connection acceptance to be processed.

  5. Repeat steps 3 & 4 to create a VIF for the secondary connection.

If you do not wish to leverage the above steps, your connection can be manually created in the AWS console by following the below steps. 

The following steps can be skipped (go to the Route Propagation section) if you have already completed the VIF creation above. 

  1. Open the AWS Direct Connect console at

  2. In the navigation pane, choose Connections.

  3. Select the Primary connection and choose Create Virtual Interface. The Create a Virtual Interface page appears.

  4. At the top of the page, select Private.

  5. In the Private Virtual Interface settings area:

    • Virtual Interface Name: Enter a name for the virtual interface.

    • Virtual Interface Owner: Select My AWS Account if the virtual interface is for your AWS account.

  6. In the Gateway type area:
    • Connection To: Select Virtual Private Gateway

    • Virtual Private Gateway: Select the your virtual private gateway.

  7. In the VLAN area:

    • VLAN: The ID is automatically set to match the Gateway VLAN in the Pureport Console and SHOULD NOT be changed.

  8. In the BGP area:

  9. Expand the Additional Settings area:
    • Address family: Select IPv4. Pureport only supports IPv4 at this time.

    • Your router peer IP: Enter the value of the Pureport IP in CIDR format from Creating a Connection.

    • Amazon router peer IP: Enter the value of the Remote IP in CIDR format from Creating a Connection.

    • BGP Authentication Key: Enter the BGP Password from Creating a Connection.

  10. Select Continue.

Repeat this process for the Secondary connection.

VPC Route Propagation

If you have not already done so, you will need to enable route propagation at the VPC level in order for your VPC(s) to announce and learn routes via BGP. Given that you are using the Virtual Private Gateway, you should only need to do this for the specific VPC that is peered with the Direct Connect VIFs.

In the AWS Console, open the VPC dashboard, click on Route Tables and select the route table which corresponds to your VPC, then click on Route Propagation to determine whether propagation is enabled:


If propagation is set to No, click the Edit route propagation button to change the setting: