AWS Direct Connect provides an alternative to the internet to connect on-premise networks to AWS. It does this through a dedicated network connection between the customer's network and an AWS Direct Connect location, bypassing the internet. Key components include virtual interfaces that enable access to AWS services, and connections that establish the dedicated network connection between the customer site and an AWS region. The presentation also covers network requirements, limits on connections and interfaces, troubleshooting tips, and resources for additional information.

1. An Introduction to
AWS Direct Connect
Presented By:
Piyush Agrawal
Date: 20th March’18

2. Agenda
• What is AWS Direct Connect?
• Key Terms and Components
• Network Requirements
• AWS Direct Connect Limits?
• Use cases and Troubleshooting
• Resources

3. Introduction to AWS Direct Connect…
• A network service that provides an alternative to using the Internet to
connect customer's on premise sites to AWS.
• AWS Direct Connect links your internal network to an AWS Direct
Connect location over a standard 1-gigabit or 10-gigabit
• With this connection in place, you can create virtual interfaces directly
to public AWS bypassing Internet service

4. Introduction to AWS Direct Connect…

5. Key Terms and Components
• Virtual Interface:
• to enable access to AWS services. A public virtual interface enables access to
public-facing services, such as Amazon S3. A private virtual interface enables
access to your VPC.
• Connection:
• a connection in an AWS Direct Connect location to establish a network
connection from your premises to an AWS region.

6. Network Requirements
• Your network is colocated with an existing AWS Direct Connect
location.
• You are working with an AWS Direct Connect partner who is a
member of the AWS Partner Network (APN).
• You are working with an independent service provider to connect to
AWS Direct Connect.

7. AWS Direct Connect Limits
• Virtual interfaces per AWS Direct Connect connection = 50 (Non
Extendable)
• Active AWS Direct Connect connections per region per account = 10
(Can be extended on request)
• Number of Direct Connect gateways per account = 200 (Can be
extended on request)

8. Use Cases and Troubleshooting
• Virtual Interface is UP, Already established a peering Session,
but can’t route the traffic over virtual Interface?
• ACL has been configured correctly for inbound/outbound traffic
• Routing table has been configured with correct public/private prefix
• Ensure the correct network prefix for public/private virtual interfaces

9. Resources
• Web Book
• https://docs.aws.amazon.com/directconnect/latest/UserGuide/dc-ug.pdf
• FAQs
• https://aws.amazon.com/directconnect/faqs/
• Videos:
• https://www.youtube.com/watch?v=eNxPhHTN8gY
• https://www.youtube.com/watch?v=uP68iqyuqTg