AWS Direct Connect with Megaport

 Download PDF

Offering Description:

Vandis will assist the customer to enable an AWS Direct Connect, a dedicated network connection from the customer’s on premise infrastructure to AWS. Using AWS Direct Connect, the client can establish private connectivity between AWS and your datacenter, office, or colocation environment, which in many cases can reduce your network costs, increase bandwidth throughput, and provide a more consistent network experience than Internet-based connections. This connection enables hybrid cloud infrastructure at the Enterprise level as well as high performance workloads. Megaport allows for programmatic connectivity to different regions as well as between AWS and other clouds and services.

Vandis’ Engineering team through this enablement establishes a dedicated network connection between the customer’s network and one of the AWS Direct Connect locations. Using industry standard 802.1q VLANs, this dedicated connection can be partitioned into multiple virtual interfaces as well as connect to a transit gateway. The client is can use the same physical connection to access Public PaaS AWS resources such as objects stored in Amazon S3 using public IP address space, and private IaaS resources such as Amazon EC2 instances running within an Virtual Private Cloud (VPC) using private IP space, while maintaining network separation between the public and private environments.

Vandis will design, configure, and deploy a Direct Connect circuit for customers as well as set up the virtual circuit on Megaport.

Prerequisites:

Customer is responsible for procuring Megaport port(s) and confirming the physical connectivity

Deliverables:

Vandis will perform the following connectivity enablement tasks to deliver a working Direct Connect circuit for a customer, either from an on premise datacenter or office to AWS:

• Conduct a network planning session
  • Evaluate NSP readiness checklist from prerequisite above
  • Work with the customer to complete any missing information in the Readiness Checklist
  • Review overall cloud strategy
  • Review deployment requirements based on checklist
  • Review desired BGP deployment end state
• Conduct a Direct Connect enablement session
  • Configure virtual circuit connectivity between the customer and the Direct Connect VGW or TGW
  • Configure BGP peering(s) between customer edge and AWS private and/or public VIF
  • Configure LAG (if applicable)
  • Conduct testing outlined in the testing criteria
• Post call and logical customer edge to AWS edge network diagram

Testing Criteria:

• Conduct testing of the private peering
       o Using a customer-provided device VM or server and a purpose-built cloud EC2 Instance, conduct testing of the following private peering metrics:
             Basic connectivity (RDP and Traceroute)
• Conduct testing of the public peering
       o Using a customer-provided device and a publicly accessible service (AWS S3, etc.), conduct testing of the following public peering metrics:
             Basic connectivity (Traceroute and file transfer)

Acceptance Criteria:

• Participation in a network planning session
• The following functionality has been verified by testing above:
       o Layer 2 connectivity
       o BGP deployment
       o Public NAT
       o Virtual circuit(s) that is connected to a single Direct Connect circuit
• Logical customer edge to AWS edge network diagram