Data Transfers with AWS DataSync
Running Operations with the Snow Family
Amazon CloudFront Design Patterns
Inter-Regional and Intra-Regional Communication Patterns
Understanding Direct Connect
The course is part of this learning path
Instructor: David Ball
Welcome to the final lecture of this course where I will summarize the key points from the previous lectures.
The Business Challenge that AWS Direct Connect Solves
I began by considering the launch of a typical cloud journey. Organizations may start small, using Amazon S3 buckets to extend backup repositories but eventually, most realize that to support production workloads on AWS, a connection will be required from their AWS VPC(s) to their on-prem data center. An IPSec VPN tunnel, using either the AWS Virtual Private Gateway or Transit Gateway service, can be setup very quickly and easily to establish this connection. However, each VPN tunnel has a maximum achievable bandwidth of 1.25 Gbps/second, but perhaps more importantly, the VPN tunnel uses the public internet which can have unpredictable and inconsistent performance, potentially making the connection unusable for latency sensitive applications.
AWS Direct Connect provides an organization the means to overcome this challenge.
AWS Direct Connect Architecture
AWS Direct Connect enables a low latency and high-speed connection to AWS services by bypassing the public internet to establish a dedicated connection from your location to AWS.
An AWS Direct Connect typically involves three entities:
- The customers business location which contains the customer-managed router or firewall to be using in connecting to AWS via Direct Connect.
- The AWS region containing resources which will be accessed over the Direct Connect.
- The Direct Connect (DX) location:
- When you order a Direct Connect, you’re ordering access to an AWS 1GB, 10GB, or 100GB network port within a Direct Connect location.
- The DX location is a regional colocation facility in which AWS rents space and has deployed some number of AWS-managed routers to serve as Direct Connect endpoints.
- The AWS Direct Connect endpoint is “cross-connected” to a customer or partner-owned and managed router once AWS has authorized the connection.
AWS Direct Connect Prerequisites and Options
As it relates to AWS Direct Connect prerequisites and options, we learned that AWS Direct Connect has specific needs that must be evaluated prior to ordering. The conditions a customer network MUST meet prior to ordering a Direct Connect:
- Direct Connect requires the use of single-mode fiber and specific transceivers based on connection speed.
- In general, auto-negotiation must be disabled, and full duplex mode must be manually set for the port(s) used for AWS Direct Connect.
- Every device across the entire Direct Connect connection must support 802.1Q VLAN encapsulation.
- The customer router serving as the Direct Connect termination point must support Border Gateway Protocol (BGP) and BGP MD5 authentication.
We also learned that Direct Connect supports:
- Asynchronous Bidirectional Forwarding Detection (BFD)
- Both IPv4 and IPv6
- An Ethernet frame size of 1522 or 9023 bytes though you must ensure that all equipment, across the entire Direct Connect connection, supports the frame size you wish to implement
How much does AWS Direct Connect cost?
Finally, we looked to answer the question, “How much does AWS Direct Connect cost?” We learned that the cost of AWS Direct Connect depends on two elements, port hours and data transfer out:
- Port hours represent the amount of time an AWS Direct Connect port has been provisioned for your use, even if no data is passing through the port.
- Data transfer out refers to the cumulative amount of data transferred through the AWS Direct Connect to destinations outside of AWS and is charged by gigabyte (GB).
That now brings me to the end of this lecture and to the end of this course, and so you should now have a greater understanding of what challenge AWS Direct Connect solves, its architecture, requirements, and potential costs.
Feedback on our courses here at Cloud Academy is valuable to both us as trainers and any students looking to take the same course in the future. If you have any feedback, positive or negative, it would be greatly appreciated if you could contact firstname.lastname@example.org.
Thank you for your time and good luck with your continued learning of cloud computing. Have a great day.
If you have any feedback, positive or negative, please contact us at email@example.com, your feedback is greatly appreciated, thank you!
This course covers the core learning objective to meet the requirements of the 'Designing Network & Data Transfer solutions in AWS - Level 2' skill
- Understand the most appropriate AWS connectivity options to meet performance demands
- Understand the appropriate features and services to enhance and optimize connectivity to AWS public services such as Amazon S3 or Amazon DynamoDB.
- Understand the appropriate AWS data transfer service for migration and/or ingestion
- Apply an edge caching strategy to provide performance benefits for AWS solutions
Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.
To date, Stuart has created 150+ courses relating to Cloud reaching over 180,000 students, mostly within the AWS category and with a heavy focus on security and compliance.
Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.
He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.
In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.
Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.