Start course
3h 55m

This section of the AWS Certified Solutions Architect - Professional learning path introduces you to the core networking concepts and services relevant to the SAP-C02 exam. We start with an introduction to the AWS Virtual Private Network (VPC) and networking services. We then understand the options available and learn how to select and apply AWS networking, DNS, and content delivery services to meet specific design scenarios relevant to the AWS Certified Solutions Architect - Professional exam. 

Want more? Try a Lab Playground or do a Lab Challenge

Learning Objectives

  • Get a foundational understanding of VPCs, their security, and connectivity
  • Learn about VPC sharing using the AWS Resource Access Manager
  • Discover inter-regional and intra-regional communication patterns in AWS
  • Learn about AWS Direct Connect, along with its implementation, configuration, and connectivity options
  • Understand routing in AWS, including static and dynamic routing
  • Understand the basics of networking, including Elastic IP addresses, Elastic Network Interfaces, networking with EC2, VPC endpoints, and AWS Global Accelerator
  • Learn about the DNS and content delivery services Amazon Route 53 and Amazon CloudFront

Welcome to the final lecture of this course, where I will summarize the key points from the previous lectures. I begin by considering a common launch of a 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 or VPCs to their on-prem data center. An IPSec VPN tunnel using either the AWS virtual private gateway or transit gateway service can be set up very quickly and easily to establish this connection. However, each VPN tunnel has a maximum achievable bandwidth of 1.25 gigabits per 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 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 customer's business location, which contains the customer manage router or firewall to be used in connecting to AWS via Direct Connect, the AWS region containing resources which will be accessed over the Direct Connect, and the Direct Connect or DX location. When you order a Direct Connect, you are ordering access to an AWS one gig, 10 gig, or 100 gig network port within a Direct Connect location. The DX location is a regional co-location 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. 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 are: One, Direct Connect requires the use of single mode fiber and transceivers based on connection speed. Two, in general, Auto-negotiation must be disabled and full duplex mode must be manually set for the ports used for AWS Direct Connect. Three, every device across the entire Direct Connect connection must support 802.1Q VLAN encapsulation. And four, the customer router serving as the Direct Connect termination point must support Border Gateway Protocol, BGP, and BGP MD5 authentication.

We also learn that Direct Connect supports asynchronous Bidirectional Forwarding Detection, or BFD. It supports both IP version 4 and IP version 6. And finally, we learned an Ethernet frame size of 1522 or 9023 bytes is supported, though you must ensure that all equipment across the entire Direct Connect connection supports the frame size you wish to implement. Finally, we look 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 per gigabyte.

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 support at Thank you for your time and good luck with your continued learning of cloud computing. Have a great day.


About the Author
Learning Paths

Danny has over 20 years of IT experience as a software developer, cloud engineer, and technical trainer. After attending a conference on cloud computing in 2009, he knew he wanted to build his career around what was still a very new, emerging technology at the time — and share this transformational knowledge with others. He has spoken to IT professional audiences at local, regional, and national user groups and conferences. He has delivered in-person classroom and virtual training, interactive webinars, and authored video training courses covering many different technologies, including Amazon Web Services. He currently has six active AWS certifications, including certifications at the Professional and Specialty level.