Menu

Lumen help

Creating an IP VPN Dynamic Connections to AWS

Using IP VPN Dynamic Connections in Control Center, you can create a connection from a Lumen IP VPN to Amazon Web Services (AWS Hosted Connection).

To create an IP VPN Dynamic Connections to AWS:

  1. Do one of the following:

    • Click Orders, then click Dynamic Connections - IPVPN. On the page that appears, click Create Connection.

    • Click Shop, then click Shop. On the page that appears, click Buy Now (under Dynamic Connections).
Dynamic Connections (IP VPN)
  1. Click Create Connection.
Dynamic Connections (Create AWS Connection)
  1. From the Customer ID and Billing Account Number lists, select the customer ID and billing account number you want to add Dynamic Connections to.

    Control Center fills in the WAN Inventory section based on your selection.
  1. In the Connection Name field, type a name for the connection you're creating.
  1. Fill in the information for the AWS connection:

    1. From the Cloud Provider list, select AWS.

    2. From the Cloud Provider On Ramp list, select an on ramp.

    3. In the AWS Account ID field, type your AWS account ID.
  1. In the WAN Inventory section, select a VRF for the other end of your connection.
  1. Use the Billing Method buttons to select whether you want monthly or hourly billing for the connection, then select the bandwidth for the connection.
  1. In the Connector Details section, fill in the additional details for the connection:

    1. From the Cloud Resource list, select whether the connection is public or private.

    2. In the AS Number on AWS field, type the autonomous system number from Amazon.

    3. From the Routing Option list, select routing option you want to use for the connection:

      • Advertise the 3 RFC 1918 aggregates to Cloud Provider (default): supports 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16. Aggregate routes will be created and the Lumen PE will be configured to advertise these aggregates toward the cloud provider gateway router on the connector-specific eBGP session.

      • Advertise All Routes, Block Specific to Cloud Provider: The Lumen PE eBGP connector session will be configured with a policy to block the advertisement of routes towards the cloud provider that contain the community 6745:8601. If you want to block specific routes, you must set this community to routes on the BGP session as the routes enter the Lumen IP VPN network (i.e. on a managed/unmanaged CPE using BGP export policy).

      • Advertise Customer-Defined Aggregates to Cloud Provider: select this option to enter your aggregate subnets. The Lumen PE will be configured to advertise these aggregates toward the cloud provider gateway router on the connector-specific eBGP session.

    4. Use the buttons to select whether you want to advertise default routes and whether this is a primary or backup connection.
  1. In the Contacts section, fill in the information for the order and technical contacts for your organization.

    1. Type the contact's first name, last name, phone number, and email address. (Be sure to use the phone number format shown on the screen.)

    2. In the Notification Preference field, select the preference for how Lumen notifies this contact of progress on your order: email, text, or both.

    3. If the technical contact for the connection is the same as the order contact, leave the checkbox selected. If the technical contact is different, clear the checkbox, then fill in the information for the technical contact.
  1. In the Connection Summary box (on the right), read through the terms and conditions, then click the checkbox to accept the terms.
  1. Click Submit.
  1. If you selected AWS and want to add resiliency for this connection, do one of the following:

    • For non-critical (production, development, test) resiliency, repeat steps 2–12 using the same VRF and same AWS on-ramp location.

    • For high resiliency, repeat steps 2–12 using the same VRF and a different AWS on-ramp location.

    • For maximum resiliency, repeat steps 2–12 three more times:

      1. Create a second connection using the same VRF and same AWS on-ramp location as the first connection.

      2. Create a third connection using the same VRF and a different AWS on-ramp location.

      3. Create a fourth connection using the same VRF and same AWS on-ramp location you used for the third connection.
         

Learn more about AWS resiliency options