All guides
Practice now
D4 · Migration and Modernization

Hybrid architectures: Direct Connect, Outposts and Local Zones

Most enterprise migrations go through a hybrid phase where on-premises and cloud resources coexist. The SAP-C02 tests designing highly available hybrid connectivity with Direct Connect, Outposts, Local Zones, and hybrid DNS patterns.

Icon-Architecture/48/Arch_AWS-Direct-Connect_48

Hybrid architectures — coexistence patterns

Cloud Bursting

The app normally runs on-premises. During demand spikes, it automatically bursts into AWS. Requires low between on-prem and AWS.

Low-latency Direct Connect, VPN as backup, hybrid DNS for routing.

Lift-and-Extend

App partially migrated to AWS. The DB stays on-premises. Or the reverse: an on-prem app accesses managed AWS services (RDS, S3).

Storage Gateway, Direct Connect, VPN, Route 53 hybrid DNS.

Full Hybrid Steady State

Permanent workloads in both environments due to compliance, ultra-low latency, or regulation. AWS and on-premises treated as first-class citizens.

AWS Outposts, redundant Direct Connect, , Shared VPCs.

Icon-Architecture/48/Arch_AWS-Direct-Connect_48

Direct Connect — and advanced patterns

provides dedicated private network connections between on-premises and AWS. Unlike VPN (which uses the internet), DX uses dedicated physical lines with dedicated bandwidth and consistent latency.

DX connection types

Dedicated Connection1/10/100 Gbps. The port is fully dedicated to the customer. Requested directly from AWS or via a partner.
Hosted Connection50 Mbps to 10 Gbps. The DX partner gives you a portion of their dedicated connection. Faster to provision (no physical fiber installation wait).
Virtual Interface (VIF)A single DX can have multiple VIFs: Private VIF (VPC), Public VIF (public AWS services), Transit VIF (Transit Gateway).

Direct Connect HA patterns

HA Level 1 (Maximum)

2 DX connections at different DX locations + 2 Customer Gateways at different datacenter locations. 4 fully independent physical paths. If an entire DX location fails, the other DX stays active.

HA Level 2 (Standard)

2 DX connections at the SAME DX location with 2 different customer devices. Protects against a single device failure, but not against the entire DX location failing.

DX + VPN Backup

Primary DX + as fallback. If DX fails, traffic uses VPN (higher latency over the internet). Cheaper than 2 DX links but with degraded performance on failover.

Direct Connect Gateway — connecting DX to multiple regions

Without a DXGW (legacy)

A DX can only connect to VPCs in the SAME region via a Virtual Gateway. For multiple regions you need multiple DX connections.

With a DXGW (recommended)

A single DX + DXGW can connect to up to 20 VGWs (Virtual Private Gateways) across up to 3 different regions. Or, via Transit VIF, connect to multiple TGWs across multiple regions.

Icon-Architecture/48/Arch_AWS-Outposts-rack_48

AWS Outposts — AWS in your datacenter

AWS Outposts brings AWS infrastructure and services into the customer's own facility. The Outposts rack is literally AWS hardware installed in your datacenter, managed remotely by AWS.

Why use Outposts

  • Ultra-low latency required (< 1ms to on-premises systems)
  • Local data residency: data that regulation requires to stay inside the datacenter
  • Legacy systems that can't tolerate network latency to the cloud
  • Manufacturing plants, hospitals, military bases without reliable internet connectivity
  • Gradual transition: use Outposts as a first step before migrating completely

Services available on Outposts

EC2EBSECSEKSRDSElastiCacheEMRS3 (Outposts)ALB/NLBVPC

Note: Not every AWS service is available on Outposts. S3 on Outposts is a separate service from S3.

Outposts requires connectivity to AWS

Outposts needs reliable connectivity to the parent AWS region for: control plane management, updates, and service sync. If connectivity is lost, existing resources keep running but new resources can't be created or modified.

Icon-Architecture/48/Arch_Amazon-EC2_48

AWS Local Zones and AWS Wavelength

AWS Local Zones

Extensions of AWS regions placed near major metropolitan areas (cities). They let you run applications with single-digit millisecond latency for users in that city.

  • Same API as AWS — EC2, EBS, VPC, RDS, ECS, etc.
  • Extension of the parent region's into the Local Zone
  • For: gaming applications, video streaming, computer-aided design (CAD), ML inference
  • Latency < 10ms to local users vs 50–100ms to the full region
  • Examples: AWS Local Zone in Buenos Aires, São Paulo, Lima, etc.

AWS Wavelength

AWS infrastructure deployed inside telecom operators' 5G networks. For applications that need single-digit millisecond latency to 5G devices.

  • Ultra-low latency (< 10ms) to 5G mobile devices
  • Traffic doesn't need to leave the operator's network
  • For: connected vehicles, AR/VR, mobile gaming, industrial IoT
  • Available in partnership with Verizon, Vodafone, KDDI, SK Telecom, etc.
  • A Wavelength Zone is an extension of the parent region
OptionTypical latencyOperated byBest for
AWS Region50–100ms (to remote users)AWS (own datacenter)Most workloads, DR, global deployment
AWS Local Zone< 10ms (to a specific city)AWS (placed near a city)Low latency for users in a specific city
AWS Outposts< 1ms (on-premises)AWS (hardware in your DC)Ultra-low latency, data residency, legacy systems
AWS Wavelength< 10ms (to 5G devices)Telecom operatorsApps for 5G mobile devices
Icon-Architecture/48/Arch_AWS-Site-to-Site-VPN_48

Advanced Site-to-Site VPN

Components and limitations

Virtual Private GatewayThe AWS side of the VPN. Attaches to a VPC. Cannot connect to multiple VPCs or to a TGW directly.
Customer GatewayThe on-premises device (router/firewall). Defined by its public IP and the routing protocol (BGP or static).
VPN Connection2 redundant IPSec tunnels per connection (high availability on the AWS side). Each tunnel terminates at a different AWS endpoint.
Bandwidth limitMaximum 1.25 Gbps per VPN connection. For more, use Direct Connect or multiple VPNs with ECMP via TGW.

Accelerated VPN — with Global Accelerator

Accelerated Site-to-Site VPN uses AWS Global Accelerator so packets enter the AWS network at the nearest edge location, reducing VPN latency and jitter.

  • Better performance for locations far from the AWS region
  • Traffic enters the AWS backbone immediately
  • Extra cost: $0.01/hour per accelerated VPN connection
  • Requires creating a new VPN connection (an existing one cannot be converted)
Icon-Architecture/48/Arch_Amazon-Route-53_48

Hybrid DNS at scale with Resolver

In hybrid environments, DNS resolution is critical — EC2 needs to resolve on-premises names and the datacenter needs to resolve VPC names and AWS service endpoints. Route 53 Resolver manages this with Endpoints and Rules.

Inbound Resolver Endpoint

ENIs in VPC subnets with private IPs. The on-premises DNS can send queries to those IPs to resolve names in the VPC's Private Hosted Zones.

→ On-premises resolves VPC names

Outbound Resolver Endpoint

Route 53 Resolver in the VPC can forward queries for certain domains (via Forward Rules) to the on-premises DNS when EC2 needs to resolve corporate names.

→ EC2 resolves on-premises names

Full hybrid DNS pattern

EC2 queries the Resolver (169.254.169.253) → Forward Rule for corp.example.com → Outbound Endpoint → on-premises DNS. A query from on-premises for vpc.example.com → on-premises DNS has a conditional forwarder → Inbound Endpoint → Route 53 Resolver → Private Hosted Zone.

Icon-Architecture/48/Arch_AWS-Direct-Connect_48

Common exam traps

Trap: "Direct Connect is more secure than VPN because it uses dedicated fiber"

Reality: Direct Connect does not encrypt traffic by default — it's only a private connection, not an encrypted one. For encryption over DX, use MACsec (at the DX layer) or an IPSec VPN over the DX public interface. VPN does encrypt with IPSec.

Trap: "AWS Outposts works with no internet or AWS region connectivity"

Reality: FALSE. Outposts requires connectivity to the AWS control plane in the parent region. Without this connectivity, new resources cannot be created, even though existing ones keep running.

Trap: "Local Zones and Availability Zones are the same thing"

Reality: They're different. AZs are datacenters within an AWS region. Local Zones are region extensions placed in specific cities — they share the region's control plane but are physically located elsewhere for lower latency to that city.

Did you get this topic?

Test what you just learned

A financial company operates in Argentina and has regulatory requirements preventing certain customer data from leaving the country. At the same time, they want to use AWS services like EC2 and RDS for a new application. The nearest AWS region is us-east-1 in Virginia. What is the most appropriate architecture?

Ready to test "Hybrid Architectures: Direct Connect, Outposts and Local Zones"?

Put what you learned to the test with original SAP-C02 exam questions.

Start SAP-C02 mock exam

Unlimited mock exams with the Pro plan

Log in to track your progress.