Lumen Cloud Connect EVPL to AWS with dedicated Direct Connect

Updated by Gavin Lai on Jan 27, 2022
Article Code: kb/1435

In this article:

Overview

The purpose of this document is to provide an end-to-end walk through for a customer setting up EVPL with Dedicated Direct Connect for the first time via Lumen’s Cloud Connect. Information contained is provided to serve as a supplement to AWS documentation linked throughout this document. Users should check the provided links to obtain the most up-to-date information and for more details pertaining to AWS processes. This document is for Cloud Connect services connecting to AWS Direct Connect with a dedicated cross connect (see diagram below). The supporting service ordered from Lumen is dedicated Cloud Connect to AWS.

aws-direct-connect-options

Audience

Users has ordered Lumen Cloud Connect to connect to their AWS environment.

Prerequisites

Lumen Cloud Connect is ordered and access to AWS Portal with the right permission

What is Direct Connect

Please refer to What is AWS Direct Connect knowledge article.

Lumen Cloud Connect EVPL to AWS

cloudconnect-aws-evpl-dedicated

  • Customer is responsible for Direct Connect costs and configuration
  • Any NAT configuration that is required due to the use of any AWS Public Services will be the responsibility of the customer.
  • All IP addressing and BGP configurations are the sole responsibility of the customer as Lumen does not participate at layer 3 routing with this service type.

Lumen Cloud Connect Roles and Responsibilities

Steps required to set up AWS Direct Connect Connectivity End Customer Lumen AWS
Set up connectivity to AWS Direct Connect location
Order Lumen Dedicated Cloud Connect service(s) to AWS Direct Connect X
Provide the LOA/CFA to your Lumen representative X
Create the virtual circuit to AWS X
Monitor the virtual circuit to AWS X
Set up BGP peering between Lumen provided edge and AWS edge device
Configure BGP Peering on Customer Layer 3 Device facing AWS X
Configure BGP peering on AWS side using console facing Lumen X
Link services on AWS to the dedicated circuit
Create and link virtual interface, virtual private gateway, VPC, Direct Connect gateway, etc. as applicable using the AWS console X

Overview of procedures to configure Lumen Cloud Connect

  1. Customer requests Lumen Cloud Connect service
  2. Creating the Direct Connect and Generating LOA CFA
  3. Creating the AWS Direct Connect from the AWS User Console
  4. Obtaining LOA CFA from the AWS User Console
  5. Lumen and Customer Provisions Cloud Connect to AWS

Procedure to Configure Lumen Cloud Connect

Customer requests Lumen Cloud Connect service

  • To order Lumen Cloud Connect to AWS Direct Connect, contact your Lumen Account Representative
  • Information needed by Lumen to complete the connection:
    • The required AWS region(s) and/or Direct Connect location(s).
  • The contractual term length is desired (1yr, 3yr, 5yr etc.).
  • Confirm you will be providing LOA/CFA to Lumen for connection at the Direct Connect location.

Creating the Direct Connect and Generating LOA CFA

For latest information, please refer to AWS Direct Connect User Guide

  • For Dedicated Cloud Connect to AWS Direct Connect service, you will need to obtain LOA/CFA from AWS via your AWS user console. To do this you first need to create an AWS Direct Connect, then select the appropriate Direct Connect Location, which will then generate an LOA/CFA.
  • Once you obtain the LOA/CFA document, please provide it to your Lumen account team immediately. This is required for the Lumen account team to submit your order for services to be provisioned.
  • Before you create the Direct Connect via the AWS user console, please ensure you have the following information:
    • The port speed that you require. You cannot change the port speed after you've created the connection request. This port speed will match that of the Lumen Cloud Connect port speed (either 1Gb or 10Gb).
    • The AWS Direct Connect location at which the connection is to be terminated. If you are not sure what these are, please consult with your Lumen representative.
    • To complete the above steps, please see instructions from the AWS website continued on the next 2 steps.

Creating the AWS Direct Connect from the AWS User Console

Depending on the resiliency options, the process can be different, the detail can be found in AWS Direct Connect User Guide.

aws-directconnect-creation

Obtaining LOA CFA from the AWS User Console

For latest information, please refer to AWS Direct Connect User Guide

aws-directconnect-obtain-loa

Important: Once you have the LOA/CFA, please email it to your Lumen Account Team as your order cannot be placed until this is receive.

Lumen and Customer Provisions Cloud Connect to AWS

  • Upon network order submission, Lumen will provision a Layer 2 Ethernet Virtual Private Line (EVPL) EVC connection to the requested interconnect point.
  • Lumen completes configuration, and provides Customer with necessary information that you will need to configure the Layer 2 turn up on the AWS side via the AWS user console:
    • Appropriate VLAN ID for each side of the circuit
    • NOTE: Lumen will configure VLAN Tagging throughout the Lumen network only. All required IP addressing and BGP routing must be configured by the customer on their layer 3 device at their premise location and also within the AWS cloud environment via their AWS user console. Customer will also be responsible for any/all NAT configurations required for AWS public services.
    • Upon provisioning completion by Lumen, you will receive the configuration information from the Lumen provisioning with instructions as to order completion, activation scheduling, etc. As applicable to your order.

Additional AWS Direct Connect and Lumen Cloud Connect Resources

Please refer to the What is AWS Direct Connect Knowledge Article for additional AWS Direct Connect resources.
For further information on Lumen Cloud Connect, please refer to product readiness page
Notes: A single Lumen Dedicated EVPL EVC Cloud Connect service will support connectivity to a multiple Virtual Interfaces (VIFs) / VPCs or a Direct Connect Gateways via Q-in-Q tagging. You will also be able to connect to AWS public services via a separate VLAN and subinterface (Q-in-Q tagging).

Support