AWS Direct Connect

5 minutes 5 Questions

AWS Direct Connect is a dedicated network service that establishes a private, high-bandwidth connection between your on-premises data center and AWS infrastructure. This service bypasses the public internet, providing more consistent network performance, reduced latency, and enhanced security for enterprise workloads. Key Components: 1. **Dedicated Connections**: Physical ethernet connections at 1 Gbps, 10 Gbps, or 100 Gbps speeds, provisioned through AWS Direct Connect locations worldwide. 2. **Hosted Connections**: Partner-provisioned connections ranging from 50 Mbps to 10 Gbps, ideal for organizations requiring smaller bandwidth allocations. 3. **Virtual Interfaces (VIFs)**: - Private VIF: Connects to VPCs using private IP addresses - Public VIF: Accesses AWS public services like S3 and DynamoDB - Transit VIF: Connects to Transit Gateways for multi-VPC architectures **Organizational Benefits**: - **Cost Optimization**: Reduces data transfer costs compared to internet-based transfers, especially for high-volume workloads - **Consistent Performance**: Provides predictable latency and throughput for mission-critical applications - **Hybrid Architecture Support**: Enables seamless integration between on-premises systems and cloud resources **High Availability Design**: For production environments, implement redundant connections across multiple Direct Connect locations. Use Link Aggregation Groups (LAG) to bundle multiple connections for increased bandwidth and failover capabilities. Consider pairing with VPN connections as a backup path. **Integration with AWS Services**: Direct Connect works with Transit Gateway to simplify connectivity across multiple VPCs and accounts. It integrates with AWS Direct Connect Gateway to access VPCs across different regions through a single connection. **Use Cases**: - Large-scale data migration projects - Real-time analytics requiring low latency - Disaster recovery solutions - Compliance requirements mandating private connectivity Understanding Direct Connect is essential for designing resilient, cost-effective hybrid architectures in complex organizational environments.

AWS Direct Connect - Complete Guide for Solutions Architect Professional Exam

Why AWS Direct Connect is Important

AWS Direct Connect is a critical networking service that establishes a dedicated, private connection between your on-premises data center and AWS. Understanding Direct Connect is essential for the Solutions Architect Professional exam because it addresses enterprise requirements for consistent network performance, reduced bandwidth costs, and enhanced security compared to internet-based connections. Many exam scenarios involve hybrid architectures where Direct Connect plays a central role.

What is AWS Direct Connect?

AWS Direct Connect is a cloud service that establishes a dedicated network connection from your premises to AWS. This connection bypasses the public internet, providing more reliable and consistent network performance. Key characteristics include:

- Dedicated Connections: Physical connections at 1 Gbps, 10 Gbps, or 100 Gbps port speeds
- Hosted Connections: Sub-1G connections (50 Mbps to 500 Mbps) or up to 10 Gbps through AWS Partners
- Virtual Interfaces (VIFs): Private VIFs for VPC access, Public VIFs for AWS public services, and Transit VIFs for Transit Gateway

How AWS Direct Connect Works

Connection Establishment:
1. You request a connection through the AWS Console at a Direct Connect location
2. AWS allocates a port at the Direct Connect location
3. You or your partner establishes a cross-connect to the AWS device
4. You create virtual interfaces to access AWS resources

Virtual Interface Types:
- Private VIF: Connects to a single VPC using private IP addresses via Virtual Private Gateway
- Public VIF: Accesses all AWS public services using public IP addresses
- Transit VIF: Connects to a Transit Gateway for access to multiple VPCs and on-premises networks

Resiliency Models:
- Maximum Resiliency: Separate connections at separate Direct Connect locations
- High Resiliency: Multiple connections at multiple locations with at least two devices per location
- Development and Test: Single connection at a single location (not for production)

Key Features and Concepts

Link Aggregation Groups (LAG): Combine multiple connections into a single managed connection using LACP protocol

Direct Connect Gateway: Enables connection to VPCs in multiple AWS Regions through a single Direct Connect connection

MACsec Encryption: Layer 2 encryption available on 10 Gbps and 100 Gbps dedicated connections

SiteLink: Enables data transfer between Direct Connect locations, bypassing AWS Regions

Bidirectional Forwarding Detection (BFD): Rapid failure detection for BGP sessions

Exam Tips: Answering Questions on AWS Direct Connect

Scenario Recognition:
- When questions mention consistent latency, dedicated bandwidth, or private connectivity, Direct Connect is likely the answer
- Questions about reducing data transfer costs for large volumes favor Direct Connect over VPN
- Hybrid architecture scenarios often require Direct Connect knowledge

Connection Type Selection:
- Choose Dedicated Connections for high bandwidth needs and full control
- Choose Hosted Connections when you need lower capacity or faster provisioning through partners
- Remember dedicated connections take weeks to months to provision

High Availability Considerations:
- Single Direct Connect connection is a single point of failure
- For production workloads, always recommend multiple connections at different locations
- VPN as backup is a common pattern for cost-effective redundancy
- For critical workloads, use two Direct Connect locations with separate connections

Multi-Region and Multi-VPC Access:
- Use Direct Connect Gateway to connect to multiple VPCs across Regions
- Use Transit VIF with Transit Gateway for complex multi-VPC architectures
- Remember Direct Connect Gateway does not enable VPC-to-VPC routing

Security Considerations:
- Direct Connect traffic is not encrypted by default
- For encryption, use VPN over Direct Connect using a Public VIF or MACsec for Layer 2 encryption
- Private VIFs use private IP addressing which provides network isolation

Cost Optimization:
- Direct Connect has lower data transfer costs compared to internet-based transfer
- Data transfer OUT over Direct Connect is cheaper than internet egress
- Port hours are charged even when no data flows

Common Exam Traps:
- Do not confuse VPN with Direct Connect - VPN uses encrypted tunnels over the internet
- Direct Connect alone does not provide encryption
- A single connection does not provide high availability
- Direct Connect Gateway connects VPCs but does not route between them

Time-Sensitive Scenarios:
- If a question requires quick setup, Direct Connect is not ideal due to long provisioning times
- Use VPN first, then Direct Connect pattern for urgent migrations
- Hosted Connections may be faster to provision than Dedicated Connections
Test mode:
More AWS Direct Connect questions
74 questions (total)

Other Design Solutions for Organizational Complexity concepts

Account structure for organizational requirementsAmazon InspectorAmazon S3 Storage LensAmazon VPC networking conceptsAutomatic failure recovery architecturesAWS Backup serviceAWS BudgetsAWS Certificate Manager (ACM)AWS CloudTrailAWS Compute OptimizerAWS container networking servicesAWS Control TowerAWS Cost ExplorerAWS Elastic Disaster RecoveryAWS Global InfrastructureAWS IAM Identity CenterAWS Key Management Service (KMS)AWS Network FirewallAWS OrganizationsAWS Pricing CalculatorAWS PrivateLinkAWS Region and Availability Zone selectionAWS Resource Access Manager (RAM)AWS Savings PlansAWS Security HubAWS Site-to-Site VPNAWS Transit GatewayAWS Trusted AdvisorCentralized logging strategiesCentralized security event notificationsCertificate management best practicesCo-location connectivityConnectivity among multiple VPCsCost allocation tagging strategiesCross-account access managementCross-account resource sharingData backup strategiesDesigning DR solutions for RTO/RPO requirementsEffective backup and restoration strategiesEncryption strategies for data at restEncryption strategies for data in transitEvaluating VPC connectivity optionsHybrid DNS with Route 53 ResolverIAM Access AnalyzerIAM policies and permissionsIAM users, groups, and rolesIP addressing and CIDR blocksKMS key policies and grantsLanding zone designMonitoring cost and usageMulti-account event notificationsMulti-account governance modelsMulti-site disaster recoveryNetwork ACLsNetwork latency requirementsNetwork segmentation and subnettingNetwork traffic monitoringOn-premises DNS integrationOn-premises to cloud integrationPilot light disaster recoveryPurchasing options impact on cost and performanceRecovery Point Objectives (RPO)Recovery Time Objectives (RTO)Reserved InstancesRoute tables for securityScale-up vs scale-out architecturesSecurity auditing strategiesSecurity groupsService Control Policies (SCPs)Spot InstancesThird-party identity provider integrationTransitive routing in AWSTroubleshooting traffic flowsVPC endpoints for service integrationsVPC Flow LogsVPC peering connectionsWarm standby disaster recovery