Leaseweb offers private connectivity to AWS services such as their VPC from selected Leaseweb data centers.
You can create a network connection from your Leaseweb services to your AWS services.
Description
Cloud Connect supports the following AWS Direct connect models:
- Hosted Virtual Interface (VIF)
- Hosted Connection
Both Direct Connect models provide access to private IP space (RFC 1918) to a Virtual Private Cloud (VPC) within AWS
Hosted VIF features:
- Managed and monitored shared customer bandwidth
- Ability to change the connection speed without an impact on service
- Supports one AWS Private Virtual Interfaces
- This model does not support Transit Gateway virtual interfaces
- AWS Direct Connect port fee is not billed through AWS
Hosted Connection features:
- Dedicated bandwidth
- Connection speed cannot be changed (a new connection will need to be created)
- Supports Private VIF or Transit VIF (from 1 Gbps connections and up)
- Support for AWS diverse ports for resiliency
- AWS Direct Connect port fee is billed through AWS
For both AWS Hosted VIF and AWS Hosted Connection, the outgoing traffic (traffic from AWS to Leaseweb) is billed through AWS.
Deploying an AWS Hosted VIF connection
The delivery of a Cloud Connect - AWS Hosted VIF order has 3 phases:
- Phase 1: Requesting information
- Phase 2: Accepting Virtual Interface in AWS console
- Phase 3: BGP configuration and testing
Phase 1
To deploy a Hosted VIF connection, we will first need some of your information. You will receive an email requesting the below details:
- AWS Account ID
- If your AWS VPC is attached to a Virtual Private Gateway, we require the Amazon side ASN of the Virtual Private Gateway
- If you have already created a Direct Connect Gateway, we require the Amazon side ASN of the Direct Connect Gateway
- If you are using another Private IP space than the default one.
If you have both a Virtual Private Gateway ASN and a Direct Connect Gateway ASN, we only require the Direct Connect Gateway ASN
Please see the instructions on AWS Documentation for how to find your AWS ID
The above information is required for us to deploy the Hosted Virtual Interface.
Phase 2
Once the the Hosted VIF has been deployed, you will need to accept the Virtual Interface in the AWS console.
We will notify you by email to accept the Interface. We will also provide the name of the interface to accept and provide the Amazon side ASN, in case you haven't created a Virtual Private Gateway or Direct Connect Gateway.
If you do not have a Virtual Private Gateway or Direct Connect Gateway, we recommend that you create one before accepting the virtual interface.
To accept the Virtual Interface in the AWS console, login to your AWS account. Under Services, go to Networking & Content Delivery, then click on Direct Connect.
In the navigation pane, click on Virtual Interfaces and then select the Virtual Interface and click Accept.
In the Accept virtual interface dialog box, select a virtual private gateway or Direct Connect gateway, and then choose 'Accept virtual interface'.
Reply to the email that the Virtual Interface has been accepted to configure BGP on our side.
Phase 3
You will be notified by email that BGP is configured, and you will be asked to test the connection.
We will provide also the Leaseweb Private IP address that we reserved to be the Gateway,
Notes:
- Please enable route propagation between AWS VPC an AWS Virtual Private Gateway.
- Please change inbound/outbound security rules to your AWS VMs to allow communication between the two environments.
- On your Leaseweb servers, please add a static route for your AWS IP space using the Leaseweb Private IP address as Gateway that we provided.
Deploying an AWS Hosted Connection
The delivery of a Cloud Connect - AWS Hosted Connection order has 3 phases:
- Phase 1: Requesting information
- Phase 2: Accepting connection and creating a Virtual Interface in the AWS console
- Phase 3: BGP configuration and testing
Phase 1
To deploy a Hosted Connection we will first need some of your information. You will receive an email requesting the below:
- AWS Account ID
- If your AWS VPC is attached to a Virtual Private Gateway, we require the Amazon side ASN of the Virtual Private Gateway
- If you have already created a Direct Connect Gateway, we require the Amazon side ASN of the Direct Connect Gateway
If you have both a Virtual Private Gateway ASN and a Direct Connect Gateway ASN, we only require the Direct Connect Gateway ASN
Please see the instructions on AWS Documentation for how to find your AWS ID.
The above information is required for us to deploy the Hosted Connection.
Phase 2
Once the new connection has been deployed you will need to accept the new connection to activate it.
We will notify you by email to accept the Connection. We will provide also the below information:
- AWS ASN
- Customer ASN
- BGP Auth key
- Customer IP address
- AWS IP Address
If you do not have a Virtual Private Gateway or Direct Connect Gateway we recommend that you create one before accepting the new connection.
Phase 3
You will be notified by email that BGP is configured, and you will be asked to test the connection.
We will provide also the Leaseweb Private IP address that we reserved to be the Gateway,
Notes:
Please enable route propagation between AWS VPC and AWS Virtual Private Gateway.
- Please change the inbound/outbound security rules to your AWS VMs to allow communication between the two environments.
- On your Leaseweb servers, please add a static route for your AWS IP space using the Leaseweb Private IP address as Gateway that we provided.
FAQs for Cloud Connect-AWS
Do you support AWS Public Virtual Interfaces?
We do not support AWS Public Virtual Interfaces in this version of Cloud Connect.