AWS Solutions Architect Learning Path

📊 Progress Dashboard

Mon, 01 Jan 0001 00:00:00 +0000

📊 Progress Dashboard#

Track your AWS SAA-C03 exam preparation progress here.

📖 Chapter Progress#

🏁 Foundation#

#	Chapter	Status
00	🧱 Prerequisites	⬜
01	🚀 Start Here	⬜
02	☁️ AWS Cloud Overview	⬜
03	🔐 IAM & Security	⬜

⚙️ Core Infrastructure#

#	Chapter	Status
04	📦 S3 & Storage Services	⬜
05	🖥️ EC2 & Compute	⬜
06	🌐 VPC & Networking	⬜
07	⚖️ ELB & Auto Scaling	⬜
08	🗄️ Database Services	⬜
09	🌍 DNS & Content Delivery	⬜

🚀 Advanced Services#

#	Chapter	Status
10	🔗 Application Integration	⬜
11	🚀 Serverless & Containers	⬜
12	🛡️ Security & Compliance	⬜
13	📊 Monitoring & Observability	⬜

⚡ Operations & Optimization#

#	Chapter	Status
14	📤 Migration & Hybrid	⬜
15	🔄 HA & Disaster Recovery	⬜
16	💰 Cost Optimization	⬜

🎯 Exam Preparation#

#	Chapter	Status
17	📝 Exam Preparation Guide	⬜
18	💼 Interview Questions	⬜
19	🏗️ Real-World Scenarios	⬜

📝 Practice Test Scores#

Test	Domain Focus	Score	%	Status
Test 1	Secure & Resilient	__/15	__%	⬜
Test 2	Performance & Cost	__/15	__%	⬜
Test 3	All Domains Mixed	__/15	__%	⬜
Test 4	All Domains Mixed	__/15	__%	⬜
Test 5	All Domains Mixed	__/15	__%	⬜
Test 6	All Domains Mixed	__/15	__%	⬜
Test 7	Final Readiness	__/15	__%	⬜

Target Score: 80%+ (12/15) on each test before exam day.

🧱 Prerequisites: Before You Start Your AWS Journey

Mon, 01 Jan 0001 00:00:00 +0000

🧱 Prerequisites: Before You Start Your AWS Journey#

This chapter covers everything you need to know before diving into AWS. If you’re from a non-technical background or need a refresher on networking, computing, and IT fundamentals — start here. These concepts are essential for understanding AWS services and for the SAA-C03 exam.

🎯 Learning Objectives#

Understand IP addressing, CIDR notation, and subnetting
Learn the OSI model and common network protocols
Grasp virtualization concepts — the foundation of cloud computing
Distinguish between block, file, and object storage
Understand relational vs NoSQL databases
Learn security fundamentals (encryption, hashing, certificates)
Differentiate cloud service models (IaaS, PaaS, SaaS)

1. Networking Fundamentals#

1.1 IP Addressing#

Every device on a network needs an IP address — like a home address for your computer.

🚀 Start Here - Your AWS SAA-C03 Journey

Mon, 01 Jan 0001 00:00:00 +0000

🚀 Start Here - Your AWS Solutions Architect Associate Journey#

Welcome! This guide is your one-stop resource to learn AWS and crack the AWS Certified Solutions Architect - Associate (SAA-C03) exam. Whether you’re a beginner with some IT background or an experienced professional looking to certify, this guide will take you step by step.

📋 Prerequisites Checklist#

Before diving into AWS, ensure you’re comfortable with these foundational topics (covered in Chapter 00: Prerequisites):

☁️ AWS Cloud Overview & Global Infrastructure

Mon, 01 Jan 0001 00:00:00 +0000

☁️ AWS Cloud Overview & Global Infrastructure#

Learning Objectives#

By the end of this chapter, you will:

Understand AWS Global Infrastructure (Regions, AZs, Edge Locations)
Navigate the AWS Management Console and CLI
Understand the AWS Well-Architected Framework
Set up billing alerts and cost management

1. AWS Global Infrastructure#

1.1 Regions#

AWS Regions are geographically distinct locations with multiple, isolated Availability Zones.

🌍 AWS Global Infrastructure

┌──────────────────────────────────────────────────────────┐
│                    AWS Cloud                             │
│                                                          │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐               │
│  │ Region 1 │  │ Region 2 │  │ Region 3 │  ...           │
│  │ (e.g.,   │  │ (e.g.,   │  │ (e.g.,   │               │
│  │ us-east- │  │ eu-west- │  │ ap-south │               │
│  │ 1)       │  │ 1)       │  │ -1)      │               │
│  └────┬─────┘  └────┬─────┘  └────┬─────┘               │
│       │             │             │                      │
│  ┌────┴─────┐  ┌────┴─────┐  ┌────┴─────┐               │
│  │ AZ 1     │  │ AZ 1     │  │ AZ 1     │               │
│  │ AZ 2     │  │ AZ 2     │  │ AZ 2     │               │
│  │ AZ 3     │  │ AZ 3     │  │ AZ 3     │               │
│  └──────────┘  └──────────┘  └──────────┘               │
│                                                          │
│  Edge Locations (PoPs) ←→ CloudFront CDN                │
│  Regional Edge Caches                                    │
└──────────────────────────────────────────────────────────┘

Key Facts:

🔐 IAM & Security

Mon, 01 Jan 0001 00:00:00 +0000

🔐 IAM & Security — Identity and Access Management#

Learning Objectives#

Understand IAM users, groups, roles, and policies
Implement least privilege and MFA
Design cross-account access patterns
Use IAM with AWS Organizations and SCPs

1. IAM Core Concepts#

1.1 What is IAM?#

AWS Identity and Access Management (IAM) lets you securely control access to AWS services and resources. It’s a global service — policies apply across all regions.

          ┌──────────────────────────────┐
          │          IAM (Global)         │
          │                              │
          │  ┌─────┐  ┌─────┐  ┌─────┐  │
          │  │Users│  │Groups│  │Roles│  │
          │  └──┬──┘  └──┬──┘  └──┬──┘  │
          │     │         │         │     │
          │  ┌──┴─────────┴─────────┴──┐ │
          │  │     Policies (JSON)      │ │
          │  └──────────────────────────┘ │
          └──────────────────────────────┘
                      │
         ┌────────────┴────────────┐
         │                         │
    ┌────┴─────┐            ┌──────┴──────┐
    │ AWS      │            │ External     │
    │ Services │            │ Identity     │
    │          │            │ (Cognito,    │
    │          │            │  SAML, LDAP) │
    └──────────┘            └─────────────┘

1.2 IAM Components#

Component	Description	Example
User	A person or service that needs access	`john.doe@example.com`
Group	Collection of users with same permissions	`Developers`, `Admins`
Role	Set of permissions assumed by a trusted entity	`EC2-S3-ReadOnly-Role`
Policy	JSON document defining permissions	`AmazonS3ReadOnlyAccess`

1.3 IAM Policy Structure#

{"Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetObject",
        "s3:ListBucket"
      ],
      "Resource": [
        "arn:aws:s3:::my-company-data-bucket/*",
        "arn:aws:s3:::my-company-data-bucket" ], "Condition": { "IpAddress": { "aws:SourceIp": "203.0.113.0/24" }
      }
    }
  ]
}

Policy Elements:

📦 S3 & Storage Services

Mon, 01 Jan 0001 00:00:00 +0000

📦 S3 & Storage Services#

Learning Objectives#

Understand S3 storage classes, lifecycle policies, and versioning
Implement S3 security (encryption, bucket policies, pre-signed URLs)
Choose between S3, EBS, EFS, and S3 Glacier based on use case
Design static website hosting and data lake architectures

1. Amazon S3 Overview#

Amazon Simple Storage Service (S3) is object storage built to store and retrieve any amount of data from anywhere. It’s 99.999999999% (11 9’s) durable.

🖥️ EC2 & Compute Services

Mon, 01 Jan 0001 00:00:00 +0000

🖥️ EC2 & Compute Services#

Learning Objectives#

Understand EC2 instance types, purchasing options, and placement groups
Configure EC2 with user data, security groups, and IAM roles
Implement Auto Scaling and load balancing
Choose between EC2, Lightsail, and Bare Metal

1. Amazon EC2 Overview#

Amazon Elastic Compute Cloud (EC2) provides virtual servers in the cloud. You can provision and scale compute capacity within minutes.

EC2 Architecture#

┌─────────────────────────────────────────────────────┐
│                    VPC / Subnet                      │
│                                                      │
│  ┌──────────────────────────────────────────────┐   │
│  │           EC2 Instance (i-abc123)             │   │
│  │                                               │   │
│  │  ┌──────────┐  ┌──────────┐  ┌──────────┐    │   │
│  │  │  vCPU    │  │  Memory  │  │  EBS     │    │   │
│  │  │  (2-128) │  │ (1-384GB)│  │  Volume  │    │   │
│  │  └──────────┘  └──────────┘  └────┬─────┘    │   │
│  │                                    │          │   │
│  │  ┌──────────┐  ┌──────────┐       │          │   │
│  │  │  ENI     │  │ Instance │       │          │   │
│  │  │ (Network)│  │  Store   │       │          │   │
│  │  └──────────┘  └──────────┘       │          │   │
│  └────────────────────────────────────┼──────────┘   │
│                                       │              │
│  ┌────────────────────────────────────┴──────────┐   │
│  │           Security Group (Firewall)            │   │
│  └───────────────────────────────────────────────┘   │
└─────────────────────────────────────────────────────┘

1.1 EC2 Instance Types#

AWS provides instance families optimized for different workloads:

🌐 VPC & Networking

Mon, 01 Jan 0001 00:00:00 +0000

🌐 VPC & Networking#

Learning Objectives#

Design VPCs with public/private subnets, NAT gateways, and route tables
Configure VPC endpoints, peering connections, and VPNs
Understand NACLs vs Security Groups
Implement multi-tier network isolation

1. Amazon VPC Fundamentals#

A Virtual Private Cloud (VPC) is your isolated network within AWS where you launch resources.

VPC Architecture#

┌────────────────────────────────────────────────────────────┐
│              AWS Region (us-east-1)                        │
│                                                            │
│  ┌──────────────────────────────────────────────────────┐  │
│  │              VPC (10.0.0.0/16)                       │  │
│  │                                                      │  │
│  │  ┌───────────────┐       ┌───────────────┐          │  │
│  │  │ Public Subnet │       │ Private Subnet│          │  │
│  │  │ 10.0.1.0/24   │       │ 10.0.2.0/24   │          │  │
│  │  │               │       │               │          │  │
│  │  │  ┌─────────┐  │       │  ┌─────────┐  │          │  │
│  │  │  │  EC2    │  │       │  │  RDS    │  │          │  │
│  │  │  │ (Public)│  │       │  │ (Private)│  │          │  │
│  │  │  └────┬────┘  │       │  └─────────┘  │          │  │
│  │  │       │       │       │               │          │  │
│  │  │  ┌────┴────┐  │       │               │          │  │
│  │  │  │  NAT GW │  │       │               │          │  │
│  │  │  └─────────┘  │       │               │          │  │
│  │  └───────────────┘       └───────────────┘          │  │
│  │                                                      │  │
│  │  ┌──────────────────────────────────────────────┐   │  │
│  │  │              Route Tables                     │   │  │
│  │  │  Public: 0.0.0.0/0 → IGW                     │   │  │
│  │  │  Private: 0.0.0.0/0 → NAT GW                 │   │  │
│  │  └──────────────────────────────────────────────┘   │  │
│  └──────────────────────────────────────────────────────┘  │
│                                                            │
│  ┌────────────┐  ┌────────────┐  ┌────────────┐          │
│  │ Internet   │  │ Direct     │  │ VPC        │          │
│  │ Gateway    │  │ Connect    │  │ Peering    │          │
│  └────────────┘  └────────────┘  └────────────┘          │
└────────────────────────────────────────────────────────────┘

1.1 VPC Components#

Component	Purpose	Example
VPC	Isolated network	`10.0.0.0/16`
Subnet	AZ-level network segment	`10.0.1.0/24` (public)
Route Table	Traffic routing rules	Routes to IGW, NAT, Peering
Internet Gateway (IGW)	Internet connectivity	Attached to VPC
NAT Gateway	Private subnet → Internet	In public subnet
Security Group	Instance-level firewall	Stateful, allow only
NACL	Subnet-level firewall	Stateless, allow+deny
VPC Endpoint	Private access to AWS services	S3, DynamoDB, SQS

1.2 CIDR & Subnetting#

VPC CIDR:     10.0.0.0/16  (65,536 IPs)
├── Public Subnet:  10.0.1.0/24  (256 IPs, us-east-1a)
├── Public Subnet:  10.0.2.0/24  (256 IPs, us-east-1b)
├── Private Subnet: 10.0.10.0/24 (256 IPs, us-east-1a)
├── Private Subnet: 10.0.11.0/24 (256 IPs, us-east-1b)
├── DB Subnet:      10.0.20.0/24 (256 IPs, us-east-1a)
└── DB Subnet:      10.0.21.0/24 (256 IPs, us-east-1b)

⚡ Exam Tip: AWS reserves 5 IPs per subnet (network, gateway, 2 AWS DNS, broadcast). So a /24 has 251 usable IPs, not 256.

⚖️ ELB & Auto Scaling

Mon, 01 Jan 0001 00:00:00 +0000

⚖️ Elastic Load Balancing & Auto Scaling#

Learning Objectives#

Choose between ALB, NLB, and CLB based on requirements
Configure target groups, listeners, and health checks
Implement Auto Scaling policies (simple, step, target tracking)
Design for high availability across AZs

1. Elastic Load Balancing (ELB)#

1.1 Load Balancer Types#

Feature	ALB (Layer 7)	NLB (Layer 4)	CLB (Legacy)
OSI Layer	7 (HTTP/HTTPS)	4 (TCP/UDP)	4 & 7
Protocols	HTTP, HTTPS, gRPC	TCP, UDP, TLS	HTTP, HTTPS, TCP, SSL
Target Type	Instance, IP, Lambda	Instance, IP, ALB	Instance only
SSL/TLS	Yes (termination)	Yes (passthrough/TCP)	Yes
WebSocket	Yes	No	No
Sticky Sessions	Yes (cookies)	No (source IP)	Yes
Fixed Response	Yes	No	No
Path-based routing	Yes	No	No
Host-based routing	Yes	No	No
Static IP	No (use NLB + Global Accelerator)	Yes (per AZ)	No
Slow start	Yes	No	No
Price	$0.0225/hr	$0.0225/hr	$0.025/hr
Use Case	Microservices, containers	TCP/UDP, extreme performance	Legacy apps

⚡ Exam Tip: ALB for HTTP/HTTPS with path-based routing. NLB for TCP/UDP with static IPs or extreme performance. CLB is legacy — avoid on new projects.

🗄️ Database Services

Mon, 01 Jan 0001 00:00:00 +0000

🗄️ Database Services#

Learning Objectives#

Choose between RDS, DynamoDB, and Aurora based on workload
Configure Multi-AZ and Read Replicas for high availability
Implement caching with ElastiCache
Understand DynamoDB table design, indexes, and DAX

1. AWS Database Landscape#

                     AWS Database Services
                            │
        ┌───────────────────┴───────────────────┐
        │                                       │
   Relational                               NoSQL
        │                                       │
   ┌────┴────┐                            ┌────┴────┐
   │ RDS     │                            │DynamoDB │
   │ ├ MySQL │                            │(KV + Doc)│
   │ ├ MariaDB│                           │         │
   │ ├ PostgreSQL│                        │ ElastiCache│
   │ ├ Oracle │                           │ ├ Redis  │
   │ ├ SQL Server│                       │ └ Memcached │
   │ └ Aurora │                           └─────────┘
   └─────────┘
        │
   ┌────┴────┐
   │ Redshift │
   │ (Data Warehouse)│
   └─────────┘

2. Amazon RDS#

2.1 RDS Overview#

Amazon Relational Database Service (RDS) makes it easy to set up, operate, and scale relational databases in the cloud.

🌍 DNS & Content Delivery

Mon, 01 Jan 0001 00:00:00 +0000

🌍 DNS & Content Delivery#

Learning Objectives#

Configure Route53 routing policies (simple, weighted, latency, geolocation, failover)
Design CloudFront distribution with custom origins and behaviors
Understand Global Accelerator vs CloudFront
Implement DDoS protection with Shield and WAF

1. Amazon Route53#

1.1 DNS Fundamentals#

Route53 is a highly available and scalable DNS web service.

User types "example.com"
    │
    ▼
┌─────────────────────────────────────────────────────┐
│                DNS Resolution                        │
│                                                      │
│  1. Browser checks cache                             │
│  2. Browser asks OS resolver                         │
│  3. OS asks ISP/Public DNS (8.8.8.8)                │
│  4. Public DNS asks Root DNS Server                  │
│     → "Find .com TLD server"                        │
│  5. Root → TLD (.com) → "Route53 is authoritative" │
│  6. TLD → Route53 → "example.com = 1.2.3.4"         │
│  7. Public DNS caches → Returns to browser           │
│  8. Browser connects to 1.2.3.4                      │
└─────────────────────────────────────────────────────┘

1.2 Route53 Routing Policies#

Policy	Description	Use Case
Simple	Single record, one destination	Basic A/AAAA/CNAME records
Weighted	Distribute % of traffic to each target	A/B testing, canary deployments
Latency	Route to lowest latency region	Global user base
Geolocation	Route based on user’s location	Regional content restrictions
Geo-proximity	Route based on distance + bias	Traffic shift between regions
Failover	Active-passive DR	Primary → Secondary (health check)
Multi-Value	Return multiple healthy IPs	Simple load balancing

Example: Weighted Routing

🔗 Application Integration

Mon, 01 Jan 0001 00:00:00 +0000

🔗 Application Integration#

Learning Objectives#

Decouple microservices using SQS, SNS, and EventBridge
Choose between pull (SQS) and push (SNS) messaging patterns
Design event-driven architectures
Implement streaming data with Kinesis

1. Amazon SQS (Simple Queue Service)#

1.1 SQS Overview#

Fully managed message queuing service for decoupling application components.

Producer → SQS Queue → Consumer
             │
        ┌────┴────┐
        │ Standard │ or │ FIFO
        │ Queue    │    │ Queue
        │          │    │
        │ At-least-│    │ Exactly-once
        │ once     │    │ processing
        │ delivery │    │ (ordered)
        │ Best-effort  │
        │ ordering  │    │
        └──────────┘    └────────┘

1.2 Standard vs FIFO Queues#

Feature	Standard	FIFO
Throughput	Unlimited	300 msg/s (3,000 with batching)
Ordering	Best-effort	Guaranteed (First-In-First-Out)
Delivery	At-least-once	Exactly-once
Deduplication	No	Yes (based on MessageDeduplicationId)
Name suffix	Any name	Must end with `.fifo`
Use Case	Order processing, notifications	Banking, financial transactions

⚡ Exam Tip: FIFO = exactly-once + ordering. Standard = high throughput + at-least-once. FIFO names must end with .fifo.

🚀 Serverless & Containers

Mon, 01 Jan 0001 00:00:00 +0000

🚀 Serverless & Containers#

Learning Objectives#

Build serverless APIs with Lambda, API Gateway, and DynamoDB
Choose between Lambda, ECS, EKS, and Fargate
Design event-driven serverless architectures
Understand container orchestration on AWS

1. AWS Lambda#

1.1 Lambda Overview#

AWS Lambda runs your code without provisioning or managing servers. You pay only for compute time consumed.

Event Sources → Lambda Function → Output
    │                              │
    │                       ┌──────┴──────┐
    │                       │ S3, DynamoDB │
    │                       │ SQS, SNS     │
    │                       │ API Gateway  │
    │                       │ Step Func.   │
    │                       └─────────────┘
    │
    ├── S3 (new object)
    ├── DynamoDB Streams
    ├── API Gateway (HTTP request)
    ├── SQS (new message)
    ├── SNS (notification)
    ├── EventBridge (scheduled)
    └── CloudWatch (logs, alarms)

1.2 Lambda Limits#

Resource	Limit
Memory	128 MB - 10,240 MB (10 GB)
Ephemeral storage	512 MB - 10,240 MB
Max execution timeout	15 minutes
Environment variables	4 KB total
Deployment package	50 MB (zipped), 250 MB (unzipped)
/tmp directory	512 MB - 10,240 MB
Concurrent executions	1,000 (soft limit, can be increased)
Invocation payload	256 KB (synchronous), 128 KB (async)

⚡ Exam Tip: Lambda max timeout is 15 minutes. For longer tasks, use ECS, Step Functions, or EC2.

🛡️ Security & Compliance

Mon, 01 Jan 0001 00:00:00 +0000

🛡️ Security & Compliance#

Learning Objectives#

Implement encryption with KMS and CloudHSM
Protect applications with WAF, Shield, and GuardDuty
Audit with CloudTrail, Config, and Inspector
Manage secrets with Secrets Manager and Parameter Store

1. AWS KMS (Key Management Service)#

1.1 KMS Overview#

KMS is a managed service for creating and controlling encryption keys.

                    ┌────────────────────────────┐
                    │        AWS KMS              │
                    │                            │
                    │  Customer Master Keys (CMK) │
                    │  ┌──────────────────────┐  │
                    │  │ AWS Managed Keys     │  │
                    │  │ (aws/s3, aws/ebs)    │  │
                    │  └──────────────────────┘  │
                    │  ┌──────────────────────┐  │
                    │  │ Customer Managed Keys│  │
                    │  │ (automatic rotation) │  │
                    │  └──────────────────────┘  │
                    │  ┌──────────────────────┐  │
                    │  │ Custom Key Store     │  │
                    │  │ (CloudHSM backed)    │  │
                    │  └──────────────────────┘  │
                    └────────────────────────────┘

1.2 KMS Key Types#

Key Type	Managed By	Auto Rotation	Use Case
AWS Managed	AWS	Yes (every 3 years)	Default encryption (S3, RDS, EBS)
Customer Managed	You	Optional (1 year)	Control over keys and policies
Custom Key Store	You (via CloudHSM)	No	FIPS 140-2 Level 3 compliance

1.3 KMS Operations#

# Create a customer managed key
aws kms create-key \
  --description "EBS encryption key for production" \
  --key-usage ENCRYPT_DECRYPT \
  --origin AWS_KMS

# Create key alias
aws kms create-alias \
  --alias-name alias/ebs-production \
  --target-key-id abcdef01-1234-5678-9abc-def012345678

# Encrypt data (up to 1 MB directly — use envelope encryption for larger)
aws kms encrypt \
  --key-id alias/ebs-production \
  --plaintext fileb://my-secret.txt \
  --output text \
  --query CiphertextBlob | base64 --decode > my-secret-encrypted.txt

# Decrypt data
aws kms decrypt \
  --ciphertext-blob fileb://my-secret-encrypted.txt \
  --output text \
  --query Plaintext | base64 --decode > my-secret-decrypted.txt

1.4 Envelope Encryption#

For data larger than 1 MB, KMS uses envelope encryption:

📊 Monitoring & Observability

Mon, 01 Jan 0001 00:00:00 +0000

📊 Monitoring & Observability#

Learning Objectives#

Monitor infrastructure with CloudWatch metrics, logs, and alarms
Audit API activity with CloudTrail
Trace requests across services with X-Ray
Centralize logs with CloudWatch Logs Insights

1. Amazon CloudWatch#

1.1 CloudWatch Metrics#

CloudWatch monitors AWS resources and applications with metrics — time-series data points.

Built-in Metrics (AWS Services):

EC2: CPUUtilization, NetworkIn, NetworkOut, StatusCheckFailed
RDS: DatabaseConnections, ReadLatency, WriteLatency
ALB: RequestCount, TargetResponseTime, HealthyHostCount
Lambda: Invocations, Duration, Errors, Throttles
S3: BucketSizeBytes, NumberOfObjects

Custom Metrics:

📤 Migration & Hybrid

Mon, 01 Jan 0001 00:00:00 +0000

📤 Migration & Hybrid Cloud#

Learning Objectives#

Plan migration strategies using the 7 Rs framework
Migrate data with DMS, DataSync, and Storage Gateway
Design hybrid connectivity with VPN and Direct Connect
Understand migration tools (SMS, MGN, Snowball)

1. The 7 Rs Migration Strategy#

graph TD
    Decision{"What's your business goal?"}
    
    Decision --> Q1{"App still needed?"}
    
    Q1 -- No --> Retire["🗑️ Retire\nDecommission unused apps\nTool: App Discovery\nRisk: None\nEffort: Minimal"]
    
    Q1 -- Yes --> Q2{"Can move as-is?"}
    
    Q2 -- Yes --> Q3{"Same hypervisor?"}
    Q3 -- Yes --> Relocate["🔄 Relocate\nMove to cloud hypervisor\nTool: AWS MGN\nRisk: Low\nEffort: Low"]
    Q3 -- No --> Rehost["🚚 Rehost (Lift & Shift)\nMove as-is to EC2\nTool: AWS MGN / SMS\nRisk: Lowest\nEffort: Quickest"]
    
    Q2 -- No --> Q4{"Minor changes acceptable?"}
    
    Q4 -- Yes --> Replatform["⚙️ Replatform\nOptimize without rewrite\nE.g., RDS instead of DB on EC2\nTool: DMS\nRisk: Low-Medium\nEffort: Medium"]
    
    Q4 -- No --> Q5{"Rebuild as cloud-native?"}
    
    Q5 -- Yes --> Refactor["🏗️ Refactor/Re-architect\nFull cloud-native rebuild\nLambda, ECS, DynamoDB\nRisk: Highest\nEffort: Most"]
    
    Q5 -- No --> Q6{"Switch to SaaS?"}
    Q6 -- Yes --> Repurchase["💼 Repurchase\nMove to SaaS product\nE.g., Salesforce, Workday\nRisk: Medium\nEffort: Medium"]
    Q6 -- No --> Retain["🏠 Retain\nKeep on-premises\nHybrid connectivity\nRisk: None\nEffort: None"]

    style Retire fill:#888,color:#fff
    style Relocate fill:#527fff,color:#fff
    style Rehost fill:#01ab5c,color:#fff
    style Replatform fill:#ff9900,color:#fff
    style Refactor fill:#d33,color:#fff
    style Repurchase fill:#1e8900,color:#fff
    style Retain fill:#666,color:#fff

Strategy	Description	Tool	RTO	Effort
Rehost (Lift & Shift)	Move as-is to EC2	AWS MGN, SMS	Hours	Low
Replatform (Lift & Optimize)	Move with minor optimizations (e.g., RDS)	DMS	Days	Medium
Refactor/Re-architect	Rebuild as cloud-native	Lambda, ECS, DynamoDB	Months	High
Repurchase	Move to SaaS product	Third-party	Months	Medium
Retire	Decommission unused apps	Application Discovery	—	Low
Retain	Keep on-premises	Hybrid connectivity	—	None
Relocate	Move to cloud-native hypervisor	AWS MGN	Hours	Low

⚡ Exam Tip: Most SAA questions focus on Rehost (quickest, least risk) and Replatform (some optimization without full rewrite).

🔄 High Availability & Disaster Recovery

Mon, 01 Jan 0001 00:00:00 +0000

🔄 High Availability & Disaster Recovery#

Learning Objectives#

Design for high availability using Multi-AZ, Multi-Region strategies
Implement disaster recovery patterns (backup, pilot light, warm standby, multi-site)
Understand RTO and RPO and how to achieve them with AWS services

1. HA & DR Fundamentals#

1.1 Key Metrics#

Metric	Description	Example
RTO (Recovery Time Objective)	Max acceptable downtime	1 hour
RPO (Recovery Point Objective)	Max acceptable data loss	15 minutes
MTBF	Mean time between failures	99.99% availability
MTTR	Mean time to recovery	Automated failover in seconds

graph LR
    subgraph Timeline["Disaster Recovery Timeline"]
        NOW["🟢 Normal Operation"]
        DISASTER["💥 Disaster Strikes\nTimestamp: T+0"]
        RESTORE["✅ System Restored\nTimestamp: T+RTO"]
    end

    DISASTER -->|RPO: Data loss window| LOSS["📉 Last Backup\nData lost since backup"]
    DISASTER -->|RTO: Recovery Time| RESTORE

    style DISASTER fill:#d33,color:#fff
    style RESTORE fill:#1e8900,color:#fff
    style LOSS fill:#888,color:#fff

    NOW -->|Time passes| DISASTER

⚡ Exam Tip: Lower RTO/RPO = higher cost. Design according to business requirements, not technical perfection.

💰 Cost Optimization

Mon, 01 Jan 0001 00:00:00 +0000

💰 Cost Optimization#

Learning Objectives#

Understand AWS pricing models and reduce costs
Use Compute Optimizer, Cost Explorer, and Trusted Advisor
Implement cost allocation tags and budgets
Choose the right pricing model for different workloads

1. AWS Pricing Models#

1.1 Compute Pricing#

Option	Discount	Commitment	Use Case
On-Demand	None	None	Short-term, spiky, unknown
Reserved Instances	Up to 72%	1 or 3 years	Steady-state workloads
Savings Plans	Up to 72%	1 or 3 years ($/hr)	Flexible across services
Spot Instances	Up to 90%	None	Fault-tolerant, batch
Dedicated Hosts	Special	1 or 3 years (per host)	BYOL, compliance

Reserved Instance Types:

📝 Exam Preparation Guide

Mon, 01 Jan 0001 00:00:00 +0000

📝 Exam Preparation Guide#

Learning Objectives#

Understand the SAA-C03 exam structure and domains
Learn proven strategies for answering scenario-based questions
Create a study plan and track your progress
Know what to expect on exam day

1. Exam Overview#

1.1 SAA-C03 Exam Details#

Detail	Information
Exam Code	SAA-C03
Cost	$150 USD
Format	Multiple choice, multiple response
Questions	65 scored questions
Time	130 minutes
Passing Score	720/1000
Languages	English, Japanese, Korean, Simplified Chinese
Delivery	Pearson VUE (test center or online proctored)
Validity	3 years

1.2 Exam Domains & Weights#

Domain	Weight	Questions
Domain 1: Design Secure Architectures	30%	~20 questions
Domain 2: Design Resilient Architectures	26%	~17 questions
Domain 3: Design High-Performing Architectures	24%	~16 questions
Domain 4: Design Cost-Optimized Architectures	20%	~13 questions

1.3 Question Types#

Multiple Choice (Single Answer) — Choose the BEST answer
Multiple Response — Select TWO or more correct answers
Scenario-based — Read a use case, choose the best architecture

Question Format Example:

💼 Interview Questions

Mon, 01 Jan 0001 00:00:00 +0000

💼 AWS Interview Questions#

This chapter contains 50+ AWS interview questions organized by topic. These are commonly asked in Solutions Architect interviews at mid-to-senior level positions.

1. General AWS Questions#

Q1: What is the difference between scalability, elasticity, and high availability?#

Answer:

Concept	Description
Scalability	Ability to handle increased load by adding resources (up/down or out/in)
Elasticity	Ability to dynamically scale resources up/down based on demand
High Availability	System designed to operate continuously without failure for extended periods

Example: Auto Scaling gives elasticity. Multi-AZ gives HA.

🏗️ Real-World Scenarios

Mon, 01 Jan 0001 00:00:00 +0000

🏗️ Real-World Scenarios#

This chapter contains real-world architecture scenarios that you’ll encounter as an AWS Solutions Architect. Each scenario includes the problem, solution, and key takeaways.

Scenario 1: E-Commerce Platform Migration#

Problem: A retail company runs their e-commerce platform on-premises. During Black Friday, traffic spikes cause outages. They want to migrate to AWS with high availability and auto-scaling.

Architecture:

CloudFront → WAF → ALB → Auto Scaling EC2 → ElastiCache → RDS Multi-AZ
                          ↓
                    SQS → Lambda (order processing) → DynamoDB
                          ↓
                    SNS → Email/SMS notifications

Solution:

📝 Practice Test 1

Mon, 01 Jan 0001 00:00:00 +0000

📝 Practice Test 1 — Domain 1 & 2 Focus#

Time: 130 minutes | Questions: 65 | Domain: Secure & Resilient Architectures

Instructions#

Choose the BEST answer for each question
Some questions have two correct answers (marked as “Select TWO”)
Mark answers, then check the answer key at the bottom
Aim for 52/65 (80%) to be exam-ready
The actual SAA-C03 exam has 65 questions in 130 minutes

Question 1#

A company is designing a web application that must be highly available across multiple Availability Zones. The application runs on Amazon EC2 instances and uses an Application Load Balancer (ALB). The data is stored in an Amazon RDS for MySQL database. Which solution provides the highest availability?

📝 Practice Test 2

Mon, 01 Jan 0001 00:00:00 +0000

📝 Practice Test 2 — Domain 3 & 4 Focus#

Time: 130 minutes | Questions: 65 | Domain: High-Performing & Cost-Optimized Architectures

Question 1#

A company runs a serverless application using Lambda functions that process data from an SQS queue. The processing time for each message is about 30 seconds. What is the maximum timeout that should be configured for the Lambda function?

A) 15 seconds B) 30 seconds C) 1 minute D) 15 minutes

📝 Practice Test 3

Mon, 01 Jan 0001 00:00:00 +0000

📝 Practice Test 3 — All Domains Mixed#

Time: 130 minutes | Questions: 65 | Domain: All Domains

Question 1#

A company needs to store application logs for 7 years to meet compliance requirements. The logs are accessed rarely (2-3 times per year) and retrieval can take up to 12 hours. Which S3 storage class is MOST cost-effective?

A) S3 Standard B) S3 Standard-IA C) S3 Glacier Deep Archive D) S3 One Zone-IA

📝 Practice Test 4

Mon, 01 Jan 0001 00:00:00 +0000

📝 Practice Test 4 — All Domains Mixed#

Time: 130 minutes | Questions: 65 | Domain: All Domains

Question 1#

A company is designing a disaster recovery strategy with an RPO of 15 minutes and an RTO of 1 hour. Which strategy meets these requirements?

A) Backup and restore with daily snapshots B) Pilot Light with data replication every 15 minutes C) Warm Standby with synchronous replication D) Multi-Site active-active

📝 Practice Test 5

Mon, 01 Jan 0001 00:00:00 +0000

📝 Practice Test 5 — All Domains Mixed#

Time: 130 minutes | Questions: 65 | Domain: All Domains

Question 1#

A company needs to provide individual users with temporary access to download specific files from S3. The access should expire after 1 hour. What is the BEST approach?

A) Make the S3 bucket public B) Generate pre-signed URLs with 1-hour expiration C) Create IAM users for each person D) Create a CloudFront signed URL with 24-hour expiration

📝 Practice Test 6

Mon, 01 Jan 0001 00:00:00 +0000

📝 Practice Test 6 — Full Length Preparation#

Time: 130 minutes | Questions: 68 | Domain: All Domains

Question 1#

A company has a web application that experiences variable traffic. The application runs on EC2 instances and uses an RDS database. To reduce costs, the company wants to ensure compute resources match demand. Which solution should be used?

A) Reserved Instances for all EC2 instances B) Auto Scaling group with target tracking policy C) Spot Instances for all workloads D) Manual scaling based on historical data

📝 Practice Test 7

Mon, 01 Jan 0001 00:00:00 +0000

📝 Practice Test 7 — Final Readiness Check#

Time: 130 minutes | Questions: 65 | Domain: All Domains (Full Simulation)

Question 1#

A company runs a global web application on EC2 instances behind an ALB in a single region. Users in other regions report high latency. What should be done to improve performance?

A) Deploy the application in additional regions with Route53 latency-based routing B) Increase the EC2 instance sizes C) Use a larger ALB D) Add more EC2 instances in the same region