Study guide
8.3 Hybrid Architecture — DNS, Storage, and Compute
AWS Solutions Architect Associate SAA-C03
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the AWS Solutions Architect Associate (SAA-C03) Exam Study Strategies and Exam Tips for SAA-C03 The AWS Well-Architected Framework
2 Domain 1: Design Secure Architectures (30%)
1.1 IAM Fundamentals — Users, Groups, Roles, and Policies 1.2 AWS Organizations, SCPs, and Multi-Account Strategy 1.3 VPC Security — Security Groups, NACLs, and VPC Endpoints 1.4 Encryption, KMS, and Secrets Management 1.5 AWS WAF, Shield, and Network Firewall 1.6 GuardDuty, Inspector, Macie, and Security Hub 1.7 The Shared Responsibility Model for Solutions Architects 1.8 Data Protection, Compliance, and Audit Services
3 Domain 2: Design Resilient Architectures (26%)
2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB 2.2 EC2 Auto Scaling — Dynamic, Predictive, and Scheduled 2.3 Multi-AZ and Multi-Region Architectures 2.4 Disaster Recovery Strategies — RTO and RPO 2.5 Decoupling with SQS, SNS, and EventBridge 2.6 AWS Step Functions and Workflow Orchestration
4 Domain 3: Design High-Performing Architectures (24%)
3.1 EC2 Instance Types, Purchasing Options, and Placement Groups 3.2 Lambda, Serverless Compute, and Container Services 3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance 3.4 Block and File Storage - EBS, EFS, and FSx 3.5 Database Services - RDS, Aurora, DynamoDB, and More 3.6 CloudFront, Route 53, and Global Accelerator 3.7 Data Ingestion and Transformation - Kinesis, Glue, and EMR
5 Domain 4: Design Cost-Optimized Architectures (20%)
4.1 Compute Cost Optimization — Right-Sizing, RIs, Savings Plans, and Spot 4.2 Storage Cost Optimization — S3 Tiers, EBS, and Data Transfer 4.3 Database Cost Optimization 4.4 AWS Cost Management and Monitoring Tools
6 VPC and Networking Deep Dive
5.1 VPC Architecture — Subnets, Route Tables, and Gateways 5.2 VPC Connectivity — Peering, Transit Gateway, and Direct Connect 5.3 Amazon API Gateway 5.4 CloudFormation and Infrastructure as Code 5.5 AWS PrivateLink and Endpoint Services
7 Migration, Transfer, and Hybrid Services
6.1 The 7 Rs of Cloud Migration 6.2 AWS Snow Family — Snowball Edge Devices 6.3 CloudWatch, CloudTrail, and AWS Config 6.4 Amazon Cognito and Identity Federation 6.5 AWS DataSync and Transfer Family
8 Serverless Architecture and Application Services
7.1 Serverless Architecture Patterns 7.2 Advanced SQS Patterns — DLQ, Backpressure, and FIFO 7.3 Analytics Services — Athena, OpenSearch, and QuickSight 7.4 Container Orchestration — ECS, EKS, and ECR
9 Advanced Topics and Exam Scenarios
8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account 8.2 Caching Strategies and ElastiCache Patterns 8.3 Hybrid Architecture — DNS, Storage, and Compute 8.4 SAA-C03 Scenario Practice — Putting It All Together
8.3 Hybrid Architecture — DNS, Storage, and Compute
Key Takeaways Explain This Topic AI
AWS Outposts puts AWS-managed racks (EC2, EBS, S3 on Outposts, RDS) in YOUR data center for low latency to local systems and data residency, billed as a capacity reservation.
Route 53 Resolver INBOUND endpoints let on-premises resolve VPC private zones; OUTBOUND endpoints plus forwarding rules let VPC resources resolve on-premises domains.
Storage Gateway provides hybrid storage with a local cache: S3 File Gateway (NFS/SMB→S3), FSx File Gateway (SMB→FSx Windows), Volume Gateway (iSCSI block, cached or stored), and Tape Gateway (VTL→Glacier).
AWS Local Zones place compute near a metro for single-digit-millisecond latency; AWS Wavelength embeds compute in 5G carrier networks for mobile-edge latency.
Connectivity choices: Site-to-Site VPN is fast to set up over the internet (encrypted); Direct Connect is a dedicated private link (consistent throughput, lower latency); pair DX with a VPN backup for an encrypted, resilient hybrid link.
Last updated: October 2026
Quick Answer: Outposts = AWS-managed racks in your data center. Route 53 Resolver : inbound = on-prem resolves VPC names; outbound = VPC resolves on-prem names. Storage Gateway = hybrid storage with a local cache (File/FSx/Volume/Tape). Local Zones = AWS compute near a metro; Wavelength = compute inside 5G carrier networks. Link on-prem to AWS with Site-to-Site VPN (fast, encrypted, over internet) or Direct Connect (dedicated, consistent, private).
AWS Outposts
AWS Outposts ships physical, AWS-managed infrastructure into your own facility so you can run select AWS services locally with the same APIs and console.
- Feature Detail
- Services EC2, EBS, S3 on Outposts, RDS, ECS, EKS, EMR (subset)
- Management AWS owns hardware, patching, and updates
- Connectivity Requires a service link back to its parent Region
- Pricing Capacity reservation (you pay for the rack, 3-year terms)
- Use cases Low latency to on-prem systems, data residency / sovereignty , local processing
Common Trap: Outposts needs connectivity to its parent Region for the control plane. If a question says the site must keep running fully disconnected for long periods, that is a Snowball Edge compute scenario, not Outposts.
Route 53 Resolver (Hybrid DNS)
- Component Direction What it enables
- Inbound endpoint On-prem → VPC On-prem DNS resolves Route 53 private hosted-zone names
- Outbound endpoint VPC → On-prem VPC resources resolve on-prem domains (e.g., corp.local )
- Resolver rules Either Conditional forwarding of specific domains to specific DNS servers
Memory hook: In bound = traffic coming into AWS to resolve AWS names; Out bound = queries leaving the VPC to reach on-prem DNS. If both directions are required, deploy both endpoints.
On the Exam: 'VPC apps must resolve app.corp.local' → outbound endpoint + forwarding rule. 'On-prem servers must resolve a private VPC record' → inbound endpoint.
AWS Storage Gateway
All gateway types keep a local cache of frequently accessed data while the bulk of data lives in AWS, giving on-prem latency for hot data and cloud durability for the rest.
- Gateway type Protocol AWS backend Use case
- S3 File Gateway NFS / SMB S3 (objects) File shares backed by S3, lifecycle to Glacier
- FSx File Gateway SMB FSx for Windows File Server Windows shares with local caching
Volume Gateway iSCSI S3 + EBS snapshots Block storage: cached (primary in S3) or stored (primary on-prem, async backup)
Tape Gateway iSCSI VTL S3 Glacier / Deep Archive Drop-in replacement for physical tape backups
On the Exam: 'Replace a physical tape library / existing backup software' → Tape Gateway . 'On-prem app needs an SMB/NFS share durably stored in S3' → S3 File Gateway . 'Back up on-prem block volumes to AWS with local low-latency reads' → Volume Gateway (cached mode).
- Edge Compute
- AWS Local Zones
- Feature Detail
- Purpose Latency-sensitive apps near a specific metro
- Services EC2, EBS, VPC, ECS, EKS, some load balancing
- Latency Single-digit milliseconds to nearby users
- Use cases Media/VFX rendering, real-time gaming, AR/VR
- AWS Wavelength
- Feature Detail
- Purpose Compute embedded in 5G carrier networks
- Latency Ultra-low for mobile devices (traffic never leaves the carrier network)
- Use cases Connected vehicles, live interactive video, edge ML inference
- Hybrid Connectivity: VPN vs Direct Connect
- Dimension Site-to-Site VPN Direct Connect (DX)
- Medium Encrypted tunnel over the public internet Dedicated private physical link
- Setup time Minutes–hours Weeks–months (provider provisioning)
- Throughput / latency Variable (internet-dependent) Consistent, predictable, lower latency
- Encryption Built-in (IPsec) Not encrypted by default — add a VPN over DX or MACsec
- Cost Low Higher (port + data)
On the Exam: 'Consistent, high-throughput, private connection' → Direct Connect . 'Need a connection quickly / as DX backup / must be encrypted' → Site-to-Site VPN . 'Resilient AND encrypted private link' → Direct Connect with a VPN backup tunnel . Connecting many VPCs and on-prem links together at scale → Transit Gateway .
Snow Family for Data Transfer
Hybrid questions sometimes hinge on moving bulk data , not steady connectivity. Pushing 100 TB over even a 1 Gbps link takes well over a week; the Snow Family ships physical, encrypted appliances instead.
- Device Capacity / role Use case
- Snowcone (discontinued Nov 2024) ~8–14 TB, small/rugged Edge collection, light transfer
- Snowball Edge Storage Optimized ~210 TB usable NVMe Bulk one-time migration
- Snowball Edge Compute Optimized Storage + EC2/Lambda Disconnected edge processing
- Snowmobile (retired Apr 2024) Exabyte-scale Massive datacenter evacuation
On the Exam: 'Transfer 80 TB to AWS where bandwidth is limited and a one-time migration is acceptable' → Snowball Edge. 'Continuous, ongoing transfer of files to S3 over the network' → DataSync (not Snow). 'Run compute at a disconnected remote site' → Snowball Edge Compute Optimized. AWS Snowball Edge is no longer available to new customers; AWS points them to AWS DataSync for online transfers, AWS Data Transfer Terminal for secure physical transfers, or AWS Partner solutions.
Putting Hybrid Together
A typical hybrid design layers these: Direct Connect (or VPN) for the network path, Route 53 Resolver endpoints for cross-environment name resolution, Storage Gateway for file/backup integration, and optionally Outposts for workloads that must stay on-prem yet use AWS APIs. Transit Gateway becomes the hub once multiple VPCs and on-prem sites must interconnect, replacing a tangle of VPC peering connections with a single hub-and-spoke router that also attaches Direct Connect gateways and VPNs.