Menu

Lumen help

Creating an IP VPN On‑Demand connection to AWS

With Lumen® IP VPN On‑Demand, you can use NaaS Manager to create a connection from a Lumen VRF to Amazon Web Services (AWS Hosted Connection). To create the connection, you'll need your AWS account ID from Amazon. Be sure to have that information handy to type in (or copy/paste). 

Note: With Amazon Web Services Hoste Connections, we recommend you create a redundant connection to qualify for better availability SLAs. 

To create an IP VPN On‑Demand connection to AWS:

  1. Click Services.

    Control Center shows the Services console. Use the console to access an inventory of your services, check the status of orders, and manage your services.
Services console
  1. In the Service Managers box, click Network-as-a-Service (NaaS).
     

The NaaS Manager Overview lists connection options. 

NaaS Manager Overview tab
  1. Click Create Connection for IP VPN On-Demand.
  1. From the Customer ID and Billing Account Number lists, select the customer number and billing account number you want to add IP VPN On-Demand to.

    NaaS Manager fills in the VRF inventory based on the customer ID and billing account number you selected. 
  1. In the Connection Name field, type a name for the connection you're creating. (Be sure to use something memorable. This name will appear on your invoice.) 
  1. In the From Location (Select Your VRF) section, select a VRF for the other end of your connection. (If there are no available VRFs for the customer number and billing account number you selected, click Create New, then type a description for the new VRF in the New VRF Description field. NaaS Manager will create the VRF when you create the connection.)
NaaS Manager Services tab
  1. From the Cloud Provider list, select AWS.
  1. Fill in the information for the AWS connection: 

    1. In the AWS Account ID field, type your AWS account ID.

    2. From the Cloud Provider On Ramp list, select an on ramp. 
  1. Click CONTINUE. 
  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. Bandwidth options are determined by the destination (to location). (You can't change the bandwidth once you create the connection. If you need to choose a different bandwidth after creating the connection, disconnect the connection and create a new one.)
NaaS Services tab
  1. Click CONTINUE.
  1. In the Select Additional Settings section, fill in the additional details for the connection:

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

    2. In the Routing Option field, select the radio button for the routing option you want to use for the connection. Learn more about routing options for an IP VPN connection 

    3. Use the buttons to select whether you want to advertise default routes and whether this is a primary or backup connection. 
NaaS Manager Services tab
  1. Click CONTINUE. 
  1. Review the order information and correct any missing or invalid selections, then click SUBMIT ORDER.

    NaaS Manager creates the request for connection, places it in Pending Activation status, and routes you to the Services tab so you can monitor the status of the connection. To see status updates, click . Once Lumen assigns the permanent VRF (within five minutes), the connection changes to Active status. 
  1. If you 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