Q. What can I do with AWS Direct Connect?
Using AWS Direct Connect, data that would have previously been transported over the Internet can now be delivered through a private network connection between AWS and your datacenter or corporate network.
Q. What are the benefits of using AWS Direct Connect and private network connections?
In many circumstances, private network connections can reduce costs, increase bandwidth, and provide a more consistent network experience than Internet-based connections.
Q. Which AWS services can be used with AWS Direct Connect?
All AWS services, including Amazon Elastic Compute Cloud (EC2), Amazon Virtual Private Cloud (VPC), Amazon Simple Storage Service (S3), and Amazon DynamoDB can be used with AWS Direct Connect.
Q. Can I use the same private network connection with Amazon Virtual Private Cloud (VPC) and other AWS services simultaneously?
Yes. Each AWS Direct Connect connection can be configured with one or more virtual interfaces. Virtual interfaces may be configured to access AWS services such as Amazon EC2 and Amazon S3 using public IP space, or resources in a VPC using private IP space.
Q. If I’m using Amazon CloudFront and my origin is in my own data center, can I use AWS Direct Connect to transfer the objects stored in my own data center?
Yes. Amazon CloudFront supports custom origins including origins you run outside of AWS. With AWS Direct Connect, you will pay AWS Direct Connect data transfer rates for origin transfer.
|AWS Direct Connect Location||AWS Region|
|CoreSite 32 Avenue of the Americas, NY||US East (Virginia)|
|CoreSite One Wilshire & 900 North Alameda, CA||US West (Northern California)|
|Equinix DC1 - DC6 & DC10||US East (Virginia)|
|Equinix FR5||EU (Frankfurt)|
|Equinix SV1 & SV5||US West (Northern California)|
|Equinix SE2 & SE3||US West (Oregon)|
|Equinix SG2||Asia Pacific (Singapore)|
|Equinix SY3||Asia Pacific (Sydney)|
|Equinix TY2||Asia Pacific (Tokyo)|
|Eircom Clonshaugh||EU (Ireland)|
|Global Switch SY6||Asia Pacific (Sydney)|
|Sinnet Jiuxianqiao IDC
|Switch SUPERNAP 8||US West (Oregon)|
|TelecityGroup, London Docklands'||EU (Ireland)|
|Terremark NAP do Brasil||South America (Sao Paulo)|
* Includes Sovereign House, Harbour Exchange 6/7, Harbour Exchange 8/9, and Meridian Gate
Q. Can I use AWS Direct Connect if my network is not present at an AWS Direct Connect location?
Yes. APN Partners supporting AWS Direct Connect can help you extend your preexisting data center or office network to an AWS Direct Connect location. Please see APN Partners for more information.
Q. How can I get started with AWS Direct Connect?
Use the AWS Direct Connect tab on the AWS Management Console to create a new connection. You will be asked to select the AWS Direct Connect location you wish to use, the number of ports, and the port speed. You will also have the opportunity to request to have an APN Partner contact you if you need assistance extending your office or data center network to the AWS Direct Connect location.
Q. Are there any setup charges or a minimum service term commitment required to use AWS Direct Connect?
There are no setup charges, and you may cancel at any time. Services provided by APN Partners may have other terms or restrictions that apply.
Q. How will I be charged and billed for my use of AWS Direct Connect?
AWS Direct Connect has two separate charges: port-hours and Data Transfer. Pricing is per port-hour consumed for each port type. Partial port-hours consumed are billed as full hours.
Data Transfer via AWS Direct Connect will be billed in the same month in which the usage occurred. If you have a hosted virtual interface, you will only be charged for the data transferred out of that virtual interface at the applicable Data Transfer rates. The account that owns the port will be charged the port-hour charges. Read more about hosted virtual interfaces here.
For AWS Direct Connect pricing information, please see AWS Direct Connect pricing. If using an APN partner to facilitate a Direct Connect connection, contact the partner regarding any fees they may charge.
Q. Will regional data transfer be billed at the AWS Direct Connect rate?
No, data transfer between Availability Zones in a Region will be billed at the regular regional data transfer rate in the same month in which the usage occurred.
Q. What defines billable port-hours?
Port-hours are billed once the connection between the AWS router and your router is established, or 90 days after you ordered the port, whichever comes first. Your welcome email will tell you the date when billing will begin. Port charges will continue to be billed anytime the AWS Direct Connect port is provisioned for your use. If you no longer wish to be charged for your port, please follow the cancellation process detailed in “How do I cancel the AWS Direct Connect service?”.
Q. How do I cancel the AWS Direct Connect service?
You can cancel AWS Direct Connect service by deleting your ports from the AWS management console. You should also cancel any service(s) offered by a third party. For example, contact the colocation provider to disconnect any cross-connects to AWS Direct Connect, and/or a network service provider who may be providing network connectivity from your remote locations to the AWS Direct Connect location.
Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax. For customers with a Japanese billing address, use of the Asia Pacific (Tokyo) Region is subject to Japanese Consumption Tax. Learn more.
Q. What connection speeds are supported by AWS Direct Connect?
1Gbps and 10Gbps ports are available.Speeds of 50Mbps, 100Mbps, 200Mbps, 300Mbps, 400Mbps, and 500Mbps can be ordered from any APN partners supporting AWS Direct Connect. Read more about APN Partners supporting AWS Direct Connect.
Q. What are the technical requirements for the connection?
AWS Direct Connect supports 1000BASE-LX or 10GBASE-LR connections over singlemode fiber using Ethernet transport. Your device must support 802.1Q VLANs. See the AWS Direct Connect User Guide for more detailed requirements information.
Q. What AWS region(s) can I connect to via this connection?
Each AWS Direct Connect location enables connectivity to the geographically nearest AWS region. You can access all AWS services available in that region.
Direct Connect locations in the US can also access the public endpoints of the other AWS regions using a public virtual interface.
Q. Are connections to AWS Direct Connect redundant?
Each connection consists of a single dedicated connection between ports on your router and an Amazon router. We recommend establishing a second connection if redundancy is required. When you request multiple ports at the same AWS Direct Connect location, they will be provisioned on redundant Amazon routers.
Q. Will I lose connectivity if my AWS Direct Connect link fails?
If you have established a second AWS Direct Connect connection, traffic will failover to the second link automatically. We recommend enabling Bidirectional Forwarding Detection (BFD) when configuring your connections to ensure fast detection and failover. If you have configured a back-up IPsec VPN connection instead, all VPC traffic will failover to the VPN connection automatically. Traffic to/from public resources such as Amazon S3 will be routed over the Internet. If you do not have a backup AWS Direct Connect link or a IPsec VPN link, then Amazon VPC traffic will be dropped in the event of a failure. Traffic to/from public resources will be routed over the Internet.
Q: What are the technical requirements for virtual interfaces to public AWS services such as Amazon EC2 and Amazon S3?
This connection requires the use of the Border Gateway Protocol (BGP) with an Autonomous System Number (ASN) and IP Prefixes. You will need the following information to complete the connection:
- A public or private ASN. If you are using a public ASN, you must own it. If you are using a private ASN, it must be in the 65000 range.
- A new unused VLAN tag that you select
- Public IPs (/30) allocated by you for the BGP session
Amazon will advertise public IP prefixes for the region via BGP. Direct Connect customers in the US will receive the public IP prefixes for all US Regions. You must advertise public IP prefixes (/30 or smaller) that you own via BGP. For more details, consult the AWS Direct Connect User Guide.
Q: What is an Autonomous System Number (ASN) and do I need one to use AWS Direct Connect?
Autonomous System numbers are used to identify networks that present a clearly defined external routing policy to the Internet. AWS Direct Connect requires an ASN to create a public or private virtual interface. You may use a public ASN which you own, or you can pick any private ASN number between 64512 to 65535.
Q. What IP address will be assigned to each end of a virtual interface?
If you are configuring a virtual interface to the public AWS cloud, the IP addresses for both ends of the connection must be allocated from public IP space you own. If the virtual interface is to a VPC, the IP address space for both ends of the connection will be allocated by AWS in the 169.254.0.0/16 range.
Q: If I have more than one virtual interface, can I exchange traffic between the two ports?
No. AWS Direct Connect can only be used to exchange traffic between your network and AWS services or your VPC.
Q: When creating a virtual interface to work with AWS services using public IP space, what IP prefixes will I receive via BGP?
You will receive all Amazon IP prefixes for the region that you are connecting to. This includes prefixes necessary to reach AWS services, and may include prefixes for other Amazon affiliates, including those of www.amazon.com. For the current list of prefixes advertised by AWS, please watch the AWS Direct Connect community forum for updates. Direct Connect customers in the US will receive the public IP prefixes for all US Regions. Standard AWS Direct Connect data transfer rates apply for all traffic routed through your AWS Direct Connect connection.
Q. What IP prefixes should I advertise over BGP for virtual interfaces to public AWS services?
You should advertise appropriate public IP prefixes that you own over BGP. Traffic from AWS services destined for these prefixes will be routed over your AWS Direct Connect connection.
Q. Can I locate my hardware next to the equipment that powers AWS Direct Connect?
You can procure rack space within the facility housing the AWS Direct Connect location and deploy your equipment nearby. However, AWS customer equipment cannot be placed within AWS Direct Connect racks or cage areas for security reasons. For more information, contact the APN Partner for the particular facility. Once deployed, you can connect this equipment to AWS Direct Connect using a cross-connect.
Q. How do I set up Direct Connect for the AWS GovCloud (US) Region?
See the AWS GovCloud (US) User Guide for detailed instructions on how to set up a Direct Connect connection for the AWS GovCloud (US) Region.
Q. What are the technical requirements for virtual interfaces to VPCs?
This connection requires the use of Border Gateway Protocol (BGP). You will need the following information to complete the connection:
- A public or private ASN. If you are using a public ASN you must own it. If you are using a private ASN, it must be in the 65000 range.
- A new unused VLAN tag that you select
- The VPC Virtual Private Gateway (VGW) id
AWS will allocate private IPs (/30) in the 169.x.x.x range for the BGP session and will advertise the VPC CIDR block over BGP. You can advertise the default route via BGP.
Q. How does AWS Direct Connect differ from an IPSec VPN Connection?
A VPC VPN Connection utilizes IPSec to establish encrypted network connectivity between your intranet and Amazon VPC over the Internet. VPN Connections can be configured in minutes and are a good solution if you have an immediate need, have low to modest bandwidth requirements, and can tolerate the inherent variability in Internet-based connectivity. AWS Direct Connect does not involve the Internet; instead, it uses dedicated, private network connections between your intranet and Amazon VPC.
Q. Can I use AWS Direct Connect and a VPN Connection to the same VPC simultaneously?
Yes. However, only in fail-over scenario's. The Direct Connect path will always be preferred, when established, regardless of AS path prepending.