Amazon Direct Connect
AWS hosted ports now support multiple AWS Virtual Private Clouds (VPCs), and are the best On Demand solution where customers require a single BGP peering with a maximum bandwidth of 500Mbps.
Where customers require 1Gbps circuit bandwidths or multiple BGP peerings, it is recommended that the dedicated port option is considered.
Amazon Direct Connect hosted ports
To create a new AWS hosted port, customers will need their AWS account number, the AWS Region they wish to connect to (e.g. EU Ireland, EU London or EU Frankfurt), the AWS Direct Connect PoP and bandwidth.
Each AWS Direct Connect PoP is linked to a parent region (e.g. EU Dublin) – but customers can establish inter region connectivity via AWS’s Direct Connect Gateway feature. For example, a hosted port in Dublin can now be used to connect to the EU Frankfurt region.
AWS support bandwidths between 50Mbps and 500Mbps on hosted ports. Hosted ports are handed over on a shared NNI and are available immediately after the incoming connection is accepted in the AWS console, after which the On Demand cloud port request is completed.
(Note – Hosted Ports are formally called Hosted Connections by AWS, the term “port” is used in the On Demand platform to avoid confusion with circuit connections)
Connections to Amazon hosted ports
Connections to AWS hosted ports are based on a 1:1 circuit connection to hosted port mapping. The cloud B end configuration is always based on single 802.1Q VLAN* – this is automatically configured when the default “Cloud VLAN” option is selected. * The Ethertype is 8100, although this is not visible to customers
The standard VLAN modes apply at the customer A end port, which are summarised in the below table:
|Application||Open port||Circuit occupies whole A end port||Port based handover, all traffic on the customer port is mapped to the AWS hosted port|
|Add VLAN||Customer uses single tagged VLAN to map traffic to AWS||VLAN added on egress, towards customer (in translation mode). VLAN can be S-VLAN (88a8) or C-VLAN (8100). Standard H&S config.|
Amazon hosted configuration
The below diagram summarises the configuration.
Handoff to AWS is via a VLAN on a single NNI - based on 802.Q tagging. Colt automatically assigns VLAN address on NNI
Ethernet circuit between Amazon NNI and A-end customer site
Handoff to customer is via a dedicated port (open mode) or via an NNI/hub (Add VLAN)
Customer is responsible for establishing BGP peering between their router & AWS. Peering assigned as 'private' or 'public' peering
Amazon Hosted Customer Journey
The customer journey to establish end to end connectivity to an AWS hosted port is illustrated below:
Amazon Direct Connect dedicated ports
AWS dedicated ports support multiple BGP peerings with AWS, each peering being based on a single AWS Virtual Interface (VIF) which in turn supports multiple Virtual Private Clouds (VPCs). Dedicated ports are the best AWS Direct Connect solution where a customer requires 1Gbps circuit bandwidths into AWS or multiple peerings at the same AWS Direct Connect location.
AWS dedicated ports (via cloud port page)
Customers will need to first request a dedicated port via the AWS subscription, taking care to select the correct AWS region and Direct Connect PoP. A Letter of Authority (LOA) is then generated within the AWS console which should be uploaded to the On Demand portal using the button provided.
*IMPORTANT – it is important that the customer selects the correct AWS region and Direct Connect PoP location within the AWS Console.*
Similar to hosted ports, each AWS Direct Connect PoP are linked to a primary region – but customers can now access multiple regions via AWS’s the Direct Connect Gateway feature.
Currently, only 1Gbps ports are supported on the On Demand platform.
Once the request has been placed, Colt’s delivery team will arrange for the cross connect between the 1Gbps Colt On Demand port and the Amazon router using the information provided within the LOA. The typical lead time for the cross connect is 10 working days.
Connections to AWS Direct Connect dedicated ports
AWS dedicated ports are based on a standard port model, which means that single or multiple circuit connections can be routed to a single AWS dedicated port.
Amazon only support 802.1Q VLANs, which means that customers are restricted to the C-VLAN option (i.e. an 8100 Ethertype) at the AWS end of the circuit Connection. AWS do not support QinQ VLAN tagging.
The standard port VLAN modes apply at the customer A end site.
Under the dedicated port model, Amazon do not impose any bandwidth on VLANs – they are dynamically scaled.
The following VLAN modes apply at the AWS B end (i.e. dedicated port end), summarised in the below table:
|Application||Open port||AWS dedicated port mapped to a single circuit connection||Port based handover, all AWS VLANs are passed transparently across the Colt network to the B end port Customer is responsible for allocating VLANs via the AWS Console (Filter VLAN option at A end site not supported)|
|Filter VLAN||AWS dedicated port is mapped to multiple circuit connections (1 VLAN/VPC per circuit)||A single VLAN is filtered at ingress to the Colt network, supporting a single VPC against each circuit connection. Customer is responsible for allocating VLANs via the AWS Console (Open port option at A end site not supported)|
|Add VLAN||AWS dedicated port is mapped to multiple circuit connections (1 VLAN/VPC per circuit)||Allows multiple circuit connections, each circuit connection to a single AWS VLAN /VPC|
Amazon dedicated port configuration
The below diagram summarises the configuration:
Handoff to AWS is via a Dedicated Port supporting multiple 802.1Q VLANs. VLANs are assigned by customer via AWS Console. Default B end option is 'Open Mode'
Ethernet circuit(s) between Amazon Dedicated Port and A-end customer site
Handoff to customer is via port based handover ('Open Mode') or via an NNI/hub (Add VLAN)
Customer is responsible for establishing NxBGP peerings between their router & AWS. Peering assigned AS 'private' (VPC) or 'public' peering
Amazon dedicated port customer journey
The customer journey to establish end to end connectivity to an AWS dedicated port is illustrated below. Note that the LOA must be requested for the correct AWS Region and AWS Direct Connect PoP associated with that region.
Amazon dedicated ports in asia pacific (and other locations)
Where an AWS location does not appear under the cloud port page (for example AWS locations in Asia Pacific, the USA and some European locations), customers can request a standard On Demand port in the required data centre and request a standard cross connect via the OD portal.
Under this option, customers are required to attach the AWS LOA to the cross connect order when requested.