AWS Direct Connect Cloud Enablement
Using AWS Direct Connect, you can establish a dedicated private network connection between AWS and your datacenter, office, or colocation environment. In many cases this 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.
Through this offering, Vandis’ Engineering team establishes a dedicated network connection between your 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. This allows you to use the same physical connection to access Public PaaS AWS resources, such as objects stored in Amazon S3, using public IP address space. You can also access private IaaS resources such as Amazon EC2 instances running within a 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.
- Customer is responsible for procuring connectivity to AWS’s Edge using an approved NSP.
- Customer is responsible for configuring their equipment to connect to the NSP.
- Customer is responsible for completing everything that is required of the Readiness Checklist from their Network Service Provider/transit provider to the best of their understanding.
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 AWS 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
- Conduct testing of the private peering
o Using a customer-provided device VM or server (IBX or connected on-premises) 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)
- 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 CSP edge network diagram
For additional information, please reach out to 516-281-2200 or firstname.lastname@example.org