Configure BGP for AWS Direct Connect

Before you begin, ensure you have completed the steps outlined in Add AWS Direct Connect to a Cloud Router. Specifically:

  • You have accepted the connection in the AWS portal.
  • You have created a virtual interface (VIF).

Gather information from AWS

  1. Go to the AWS Console Virtual Interfaces page and select the virtual interface associated with the PacketFabric connection.

  2. From the virtual interface details page, gather the following information:

    • Amazon side ASN
      Note: This is also the ASN of the associated AWS gateway.

    • Your router peer IP

    • Amazon router peer IP

    Screenshot of the AWS virtual interface page

Add BGP information to the Cloud Router connection

  1. After completing the steps above, return to the Cloud Routers page in the PacketFabric portal.

  2. Click the Cloud Router to expand its connections.

  3. Click Configure BGP.

    Screenshot of the Configure button in the PacketFabric portal

Complete the following fields:

BGP Settings
  • Header row
    • Field
    • Description
  • Row 1
    • PacketFabric ASN

    • This is the ASN you specified when creating your PacketFabric Cloud Router. You cannot edit this field.

      When you create the virtual interface from the AWS Console, you enter this ASN into the BGP ASN field.

  • Row 1
    • Amazon ASN

    • Enter the Amazon-side ASN associated with the virtual interface.

      You specify this ASN when you create the AWS Direct Connect Gateway or the AWS Virtual Private Gateway. Public virtual interfaces use ASN 7224.

  • Row 1
    • PacketFabric Router Peer IP
    • Enter Your router peer IP generated with the AWS virtual interface.
  • Row 1
    • Amazon Router Peer IP
    • Enter the Amazon router peer IP generated with the AWS virtual interface.
  • Row 1
    • MD5 (Optional)
    • Enter the BGP authentication key generated with the virtual interface.
  • Row 1
    • Allow longer prefixes

    • This applies to the allowed incoming and outgoing prefixes that you list below.

      For example, say you list 172.16.2.0/24 as an allowed incoming prefix. You have three other cloud connections with the following outgoing prefixes:

      Connection A: 172.16.2.0/24
      Connection B: 172.16.0.0/16
      Connection C: 172.16.2.128/25

      If you do not select this option, only routes from Connection A are allowed.

      If you select this option, the routes from Connection A and Connection C are allowed.

Allowed prefixes to cloud

This is a list of addresses that you want to allow into your AWS VPC. These can be addresses from other cloud environments or from a different AWS VPC.

  • Row
    • Field
    • Description
  • Row
    • ASN prepend

    • Number of additional times to add the ASN to the BGP path, resulting in a higher path length.

      Routes with higher path length (a higher ASN prepend value) have a lower priority.

  • Row
    • MED

    • The multi-exit discriminator (MED) value.

      When the same route is advertised in multiple locations, those with a lower MED are preferred by the peer AS.

  • Row
    • Prefix/Mask
    • Enter an allowed IP address range in CIDR format. You can add up to 1000 prefixes.
IMPORTANT: If you are using a public virtual interface, all incoming traffic must originate from the same public IP block you specified in the Your router peer ip field when creating the virtual interface. This means you might need to use NAT options in other clouds.
Allowed prefixes from cloud

This is a list of addresses from within the AWS environment that you want to advertise to other clouds. This can include the VPC internal space and any routes you have created.

  • Row
    • Field
    • Description
  • Row
    • Local preference
    • When the same route is received in multiple locations, those with a higher local preference value are preferred by the PacketFabric Cloud Router.
  • Row
    • Prefix/Mask
    • Enter an allowed IP address range in CIDR format. You can add up to 1000 prefixes.