AWS Certified Solutions Architect – Associate

Exam code SAA-C03. This single page holds two things: a fast high-level overview to orient you, and a brief study guide to understand which topics to study covering every exam domain, the in-scope services, decision tables, and community-recommended study materials. Overview items link straight into their deep-dive sections.

65 questions 130 minutes 720/1000 to pass $150 USD Valid 3 years
⚡ Open the 1-page Cram Jam sheet

Part 1 — High-Level Overview

What & Why

The AWS Certified Solutions Architect – Associate validates your ability to design solutions on AWS that are secure, resilient, high-performing, and cost-optimized — the four pillars it borrows from the AWS Well-Architected Framework. It is AWS's most popular certification and the standard "prove you can design on AWS" credential for cloud engineers, architects, and developers.

You are not expected to write code or deep-configure every service. You are expected to read a business scenario and pick the right combination of services and the right configuration. The exam is a giant "which option best meets these requirements?" quiz.

Who it's for AWS recommends ~1 year of hands-on experience designing on AWS. If you have no IT background, start with Cloud Practitioner (CLF-C02) first. Full detail in §1 Exam Details.

Exam at a Glance

AttributeValue
Exam codeSAA-C03
Questions65 total — 50 scored + 15 unscored (pretest, not identified)
Question typesMultiple choice (1 of 4) & multiple response (2+ of 5+)
Time130 minutes
Passing score720 out of 100–1000 (scaled, compensatory)
Cost150 USD (practice question set is free on AWS Skill Builder)
DeliveryPearson VUE test center or online proctored
Validity3 years

→ Deep dive: §1 Exam Details & Logistics

The 4 Domains

The exam is organized into four weighted domains. Security is the single biggest chunk — study it accordingly.

30%
Domain 1 — Design Secure Architectures
26%
Domain 2 — Design Resilient Architectures
24%
Domain 3 — Design High-Performing Architectures
20%
Domain 4 — Design Cost-Optimized Architectures
DomainWhat it testsDeep dive
1 · Secure 30%IAM & identity federation, multi-account governance, encryption/KMS, VPC security, protecting apps from threats.→ §4
2 · Resilient 26%Loose coupling & messaging, scaling, serverless & containers, high availability, disaster recovery.→ §5
3 · High-Performing 24%Choosing performant storage, compute, databases, networking, and data ingestion/analytics.→ §6
4 · Cost-Optimized 20%Right-sizing and cheapest-fit storage, compute, database, and network + cost tooling.→ §7

Core Services Snapshot

If you master this shortlist you cover the majority of questions. Each links to its detailed treatment.

Compute

EC2 (+ Auto Scaling), Lambda, ECS/EKS/Fargate, Elastic Beanstalk, Batch. → details

Storage

S3 (+ storage classes), EBS, EFS, FSx, Storage Gateway, Snow Family. → details

Database

RDS, Aurora, DynamoDB, ElastiCache, Redshift, DocumentDB, Neptune. → details

Networking

VPC, subnets, SG/NACL, Route 53, CloudFront, ELB, Direct Connect, VPN, PrivateLink, Transit Gateway. → details

Security & Identity

IAM, Organizations/SCPs, KMS, ACM, Secrets Manager, WAF, Shield, GuardDuty, Cognito. → details

Integration

SQS, SNS, EventBridge, Step Functions, API Gateway, Kinesis. → details

→ Full in-scope service reference by category (§8)

Recommended Materials (community consensus)

Synthesized from many r/AWSCertifications threads. The overwhelmingly common formula is one video course + one practice-exam bank, hammered until you consistently score 80%+.

The consensus stack: pick Stephané Maarek (Udemy) or Adrian Cantrill for the main course → then drill Tutorials Dojo / Jon Bonso practice exams → use Tutorials Dojo cheat sheets for review. That trio is recommended more than everything else combined.

→ Full breakdown with sources, alternatives & frequencies (§10)

Study Plan (Quick Version)

Built on learning science — active recall + spaced repetition beat passive re-watching. Test yourself early and often; don't just consume.

  1. Weeks 1–3: Watch a full video course, doing hands-on labs. After each section, close the notes and recall it; make flashcards.
  2. Week 4: Deep-dive the highest-weight/trickiest domains (Security, Cost). Teach each domain out loud (Feynman); sketch architectures from memory. Daily spaced flashcard review.
  3. Weeks 5–6: Practice exams in review mode, interleaved; study every wrong answer's explanation and turn misses into flashcards. Repeat to consistent 80%+.
  4. Final days: Free AWS official practice questions, skim WAF pillars & the Cram Jam, sleep well — don't cram new material.

→ Detailed retention-based plan (§11)  ·  ⚡ Cram Jam one-pager  ·  → Exam-day tips & traps (§12)

Part 2 — Thorough Study Guide

1 · Exam Details & Logistics

The SAA-C03 exam "validates a candidate's ability to design solutions based on the AWS Well-Architected Framework." Concretely, AWS says it validates your ability to:

  • Design solutions that incorporate AWS services to meet current business requirements and future projected needs.
  • Design architectures that are secure, resilient, high-performing, and cost-optimized.
  • Review existing solutions and determine improvements.

Scoring mechanics

  • 65 questions, only 50 are scored. The other 15 are unscored "pretest" items AWS is trialing — they are not marked, so treat every question as if it counts.
  • Scaled score 100–1000, pass at 720. It is compensatory: you do not need to pass each domain individually, only the overall exam. A strong domain can offset a weak one.
  • No penalty for guessing — never leave a question blank. Unanswered = incorrect.
  • Question formats: multiple choice (1 correct + 3 distractors) and multiple response (select 2+ from 5+). Distractors are deliberately plausible.

Target candidate

At least 1 year of hands-on experience designing cloud solutions with AWS. Candidates with 1–3 years of general IT experience have prepared successfully. With no IT experience, earn Cloud Practitioner first.

Logistics

ItemDetail
Price150 USD (plus local taxes / FX). A 50% discount voucher is often available after passing any other AWS exam.
LanguagesEnglish, French, Italian, Japanese, Korean, Portuguese (BR), Spanish (LatAm & Spain), Simplified & Traditional Chinese.
DeliveryPearson VUE testing center, or online proctored from home (quiet private room, webcam, ID check).
RecertificationValid 3 years. Recertify by re-passing the current exam, or automatically by earning the Solutions Architect – Professional.

↑ back to top

2 · AWS Well-Architected Framework

The entire exam is a practical test of the WAF. Know the pillars — many "best practice" questions are really asking "which pillar principle applies?"

PillarCore ideaKey mechanisms
Operational ExcellenceRun & monitor systems, continuously improve.IaC (CloudFormation), CloudWatch, small reversible changes, runbooks.
SecurityProtect data, systems, assets.Least privilege IAM, encryption, detective controls (GuardDuty/Config), shared responsibility.
ReliabilityRecover from failure, scale to meet demand.Multi-AZ, Auto Scaling, health checks, backups, DR strategies.
Performance EfficiencyUse resources efficiently as demand changes.Right service selection, serverless, caching, global reach.
Cost OptimizationAvoid unnecessary cost.Right-sizing, purchasing models, managed services, lifecycle policies.
SustainabilityMinimize environmental impact.Managed services, right-sizing, efficient regions/instances.
Shared Responsibility Model AWS is responsible for security OF the cloud (hardware, global infrastructure, managed-service software). You are responsible for security IN the cloud (your data, IAM, OS patching on EC2, network/firewall config, encryption choices). The line shifts toward AWS as you move from EC2 → managed (RDS) → serverless (Lambda/S3).

↑ back to top

3 · AWS Global Infrastructure

  • Region — a physical geographic area (e.g. us-east-1). Isolated; you pick regions for latency, compliance/data residency, cost, and service availability. Most services are region-scoped.
  • Availability Zone (AZ) — one or more discrete data centers in a Region, with independent power/cooling/networking, connected by low-latency links. Deploy across ≥2 AZs for high availability.
  • Edge Locations / PoPs — hundreds of sites used by CloudFront, Route 53, Global Accelerator, and AWS WAF for low-latency delivery and DDoS absorption.
  • Local Zones — infrastructure closer to large population centers for single-digit-ms latency. Wavelength embeds compute in 5G networks. Outposts puts AWS hardware in your data center.
Scope cheat Global: IAM, Route 53, CloudFront, WAF, Organizations. Region: VPC, S3 (bucket namespace is global but data lives in one region), DynamoDB, RDS. AZ: EC2 instances, EBS volumes, subnets.

↑ back to top

4 · Domain 1 — Design Secure Architectures 30%

The largest domain. It spans three official task statements: (1.1) secure access to AWS resources, (1.2) secure workloads & applications, and (1.3) appropriate data security controls.

4.1 · IAM & Identity

IAM (Identity and Access Management) controls who can do what to which resources. It is global, free, and central to the exam.

Building blocks

  • Users — long-term identities for a person/app. Groups — collections of users; attach policies to groups, not individual users.
  • Roles — temporary credentials assumed by trusted principals (EC2, Lambda, other accounts, federated users). Prefer roles over long-lived access keys. An EC2 instance profile passes a role to an instance so apps never store keys.
  • Policies — JSON documents (Effect, Action, Resource, optional Condition). Types: identity-based (on users/groups/roles), resource-based (on S3 buckets, SQS, KMS, etc., with a Principal), permissions boundaries, and SCPs (org guardrails).

Policy anatomy

Every policy statement is built from the same four elements — being able to read one fast pays off across many questions:

  • Effect — Allow or Deny.  Action — the API calls covered (s3:GetObject, ec2:*).  Resource — the ARNs it applies to (arn:aws:s3:::my-bucket/*).
  • Condition (optional) — context tests: aws:SourceIp (restrict by IP), aws:MultiFactorAuthPresent (require MFA), aws:PrincipalOrgID (only principals from your Organization), s3:x-amz-server-side-encryption (require encrypted uploads).

Evaluation logic (know this cold)

  • Explicit Deny always wins over any Allow.
  • Default is implicit deny; you need an explicit Allow somewhere.
  • Effective permissions = intersection of SCPs, permissions boundaries, and identity/resource policies. An SCP that doesn't allow an action blocks it even if IAM allows it.
  • Same-account: access is granted if either the identity policy or the resource policy allows it. Cross-account: both sides must allow (identity policy in the caller's account and the resource policy / trust policy in the target account).
  • IAM Access Analyzer continuously finds resources (buckets, roles, KMS keys) shared with external entities — the answer to "identify unintended external access."

Federation & temporary access

  • AWS STS issues temporary security credentials (AssumeRole, AssumeRoleWithSAML, AssumeRoleWithWebIdentity). Used for role switching and cross-account access.
  • IAM Identity Center (successor to AWS SSO) — central workforce sign-on across many accounts & apps; integrates with external IdPs (Okta, Azure AD) and Active Directory.
  • AWS Directory Service — managed Microsoft AD; federate an on-prem directory with IAM roles rather than recreating users.
  • Amazon Cognito — identity for customer-facing apps: User Pools (sign-up/sign-in, JWT tokens) and Identity Pools (exchange tokens for temporary AWS credentials).
Common trap "App on EC2 needs to access S3" → attach an IAM role to the instance, never hard-code access keys. "Users in Account A need to use resources in Account B" → cross-account IAM role + sts:AssumeRole, not new users.
Best practices Enable MFA (especially on root); lock away root credentials and use it almost never; grant least privilege; use roles & groups; rotate credentials; use IAM Access Analyzer to find resources shared externally.

4.2 · Multi-Account & Organizations

ServicePurpose
AWS OrganizationsCentral management of many accounts; consolidated billing; organize accounts into OUs.
Service Control Policies (SCPs)Org-wide guardrails — the maximum permissions available in member accounts. They do not grant access; they set a ceiling. Applied to OUs/accounts.
AWS Control TowerAutomated setup of a secure, multi-account landing zone with best-practice guardrails, a Log Archive account, and Audit account.
AWS RAM (Resource Access Manager)Share resources (subnets, Transit Gateway, License Manager configs) across accounts without duplicating them.
AWS IAM Identity CenterSingle sign-on to all accounts & assigned permission sets.
When to use what Need to restrict what an entire OU can ever do (e.g. block a region, deny disabling CloudTrail)? → SCP. Need to stand up a governed multi-account environment fast? → Control Tower. Need one bill & volume discounts? → Organizations consolidated billing.

4.3 · Data Protection & Encryption

Encryption at rest

  • AWS KMS — managed keys for encrypting data across services (S3, EBS, RDS, etc.). AWS-managed, customer-managed (CMK), and AWS-owned keys. CMKs let you control rotation and key policies. Automatic annual rotation is available for CMKs. KMS uses envelope encryption (a data key encrypts data; KMS encrypts the data key).
  • CloudHSM — dedicated, single-tenant, FIPS 140-2 Level 3 hardware security module when you need full control of keys / regulatory mandates.
  • Enable encryption per service: S3 (SSE-S3, SSE-KMS, SSE-C, DSSE-KMS), EBS volume encryption, RDS/Aurora encryption (must be set at creation), DynamoDB encryption at rest (default).

Encryption in transit

  • ACM (AWS Certificate Manager) — free public TLS/SSL certificates for ELB, CloudFront, API Gateway; auto-renews. Certs are regional (CloudFront requires us-east-1).
  • Use HTTPS/TLS everywhere; terminate TLS at ALB/CloudFront.

Secrets & config

  • AWS Secrets Manager — store DB credentials/API keys with automatic rotation (built-in for RDS). Costs per secret.
  • SSM Parameter Store — store config & secrets (SecureString via KMS); cheaper, no built-in rotation. Good default when you don't need rotation.

Data governance & discovery

  • Amazon Macie — ML-based discovery of sensitive data (PII) in S3.
  • AWS Config — records resource configuration & compliance over time.
  • AWS Artifact — self-serve compliance reports (SOC, PCI, ISO).
Exam signals "Rotate DB credentials automatically" → Secrets Manager. "Discover PII/credit-card data in S3" → Macie. "Managed HSM / dedicated tenancy / FIPS 140-2 L3" → CloudHSM. "Free auto-renewing TLS cert" → ACM.

4.4 · Network & Application Security

VPC security controls

Security GroupNetwork ACL
LevelInstance / ENISubnet
StateStateful (return traffic auto-allowed)Stateless (must allow return traffic explicitly)
RulesAllow onlyAllow and Deny
EvaluationAll rules evaluatedRules processed in number order, first match wins
  • Public vs private subnets — a subnet is "public" if its route table sends 0.0.0.0/0 to an Internet Gateway. Private subnets reach the internet outbound via a NAT Gateway (in a public subnet).
  • VPC endpoints keep traffic to AWS services on the AWS network: Gateway endpoints (S3, DynamoDB — free, route-table based) and Interface endpoints / PrivateLink (ENI in your subnet, most other services).
  • AWS Network Firewall — managed stateful network firewall for a VPC. Firewall Manager — central management of WAF/Shield/SG rules across accounts.

VPC facts worth memorizing

  • VPC CIDR size: /16 (65,536 IPs) down to /28 (16 IPs); you can add secondary CIDR blocks.
  • Each subnet reserves 5 IP addresses (network, VPC router, DNS, future use, broadcast) — a /28 subnet has 11 usable hosts.
  • Security groups can reference other security groups — the standard tier-to-tier pattern (app-tier SG allows MySQL only from the web-tier SG), no IP lists to maintain.
  • VPC Flow Logs capture accepted/rejected IP traffic metadata (not packet contents) at VPC, subnet, or ENI level → CloudWatch Logs or S3. The answer to "analyze / troubleshoot network traffic."
  • Admin access to private instances: prefer SSM Session Manager (no inbound ports, no bastion host, sessions logged) when the ask is "most secure / least management."
  • Egress-only Internet Gateway — outbound-only internet for IPv6 (the IPv6 equivalent of a NAT gateway).

Application & threat protection

ServiceProtects against / does
AWS WAFLayer-7 filtering of HTTP(S) — SQL injection, XSS, rate limiting, geo-blocking. Attaches to ALB, CloudFront, API Gateway, AppSync.
AWS ShieldDDoS protection. Standard is free & automatic; Advanced ($) adds L3/4/7 protection, 24/7 DRT, and cost-protection.
Amazon GuardDutyIntelligent threat detection from CloudTrail, VPC Flow, DNS logs (no agents).
Amazon InspectorAutomated vulnerability assessment for EC2, ECR images, Lambda.
Amazon DetectiveInvestigate/visualize the root cause of security findings.
AWS Security HubAggregates & prioritizes findings across security services against standards (CIS, etc.).
Don't mix these up WAF = app-layer web exploits & rules. Shield = DDoS. GuardDuty = detect threats/anomalies. Inspector = find vulnerabilities/CVEs. Macie = find sensitive data in S3. Security groups/NACLs = network access control.

↑ back to top

5 · Domain 2 — Design Resilient Architectures 26%

Two task statements: (2.1) scalable & loosely coupled architectures, and (2.2) highly available and/or fault-tolerant architectures.

5.1 · Decoupling & Messaging

Loose coupling means components fail or scale independently. Insert a queue, topic, or event bus between tiers so a slow/failed consumer doesn't take down the producer.

ServicePatternKey facts
Amazon SQSQueue — decouple producers/consumers (pull)Standard: near-unlimited throughput, at-least-once, best-effort ordering. FIFO: exactly-once, strict order. Msg retention 4 days default (max 14). Visibility timeout (default 30s, max 12h). Long polling (≤20s) cuts empty receives. DLQ for poison messages.
Amazon SNSPub/Sub — fan-out (push)Topics push to many subscribers (SQS, Lambda, HTTP, email, SMS). SNS + SQS fan-out = one event to many queues.
Amazon EventBridgeEvent bus — routing & SaaS eventsRules route events to targets; schema registry; connects AWS + SaaS + custom apps. Schedule cron-style tasks.
AWS Step FunctionsWorkflow orchestrationState machine coordinating multiple services with retries, branching, human-approval. Standard vs Express workflows.
Amazon MQManaged message brokerFor existing apps using standard protocols (JMS, AMQP, MQTT) migrating to AWS. Otherwise prefer SQS/SNS.
Amazon API GatewayManaged API front doorREST/HTTP/WebSocket APIs, throttling, auth, caching; fronts Lambda/HTTP backends.

Know the numbers & variants

ServiceDetails the exam actually tests
SQSMax message 256 KB. Messages aren't deleted on read — the consumer must delete after processing; the visibility timeout hides in-flight messages (too short → duplicates, too long → slow retry). FIFO: 300 msg/s (3,000 batched), requires message group ID.
API GatewayREST API = full features (API keys, usage plans, request validation, per-stage caching). HTTP API = cheaper & lower latency, fewer features — default for simple Lambda proxying. 29-second integration timeout — long jobs should go async (SQS/Step Functions), not through API GW.
Step FunctionsStandard: up to 1 year, exactly-once — long-running, auditable workflows. Express: up to 5 min, at-least-once, high-volume/cheap — event processing at scale.
SNSSubscription filter policies deliver only matching messages per subscriber — filter at SNS instead of in consumer code. FIFO topics pair with SQS FIFO for ordered fan-out.
Lambda + SQSLambda polls SQS for you (event source mapping) — the classic serverless buffer: API → SQS → Lambda, with a DLQ for poison messages.
Signal words "Decouple", "buffer", "absorb spikes", "process later" → SQS. "Notify multiple systems", "fan-out" → SNS (often + SQS). "React to events / route by content / from SaaS" → EventBridge. "Coordinate multi-step workflow with retries" → Step Functions. "Exactly-once & ordered" → SQS FIFO.

5.2 · Scaling, Serverless & Containers

Scaling concepts

  • Vertical scaling — bigger instance (scale up); limited, requires downtime.
  • Horizontal scaling — more instances (scale out); preferred for resilience & elasticity.
  • EC2 Auto Scaling Group (ASG) — maintains desired capacity across AZs, replaces unhealthy instances, and scales on policies: target tracking (keep CPU at 50%), step, simple, and scheduled. Combine with ELB health checks. Predictive scaling uses ML.
  • ASG details that get tested: min/desired/max capacity; launch templates (preferred over legacy launch configurations); lifecycle hooks run custom actions while instances launch/terminate; a default cooldown/warm-up prevents thrashing; set the ASG to use ELB health checks so app-level failures (not just instance failures) trigger replacement.
  • Design instances to be stateless — externalize session state to DynamoDB/ElastiCache so any instance can serve any request. Use sticky sessions on the ALB only when you can't (it fights even load distribution).

Serverless

  • AWS Lambda — run code without servers; pay per request & ms. Max 15-min timeout, memory 128 MB–10,240 MB (CPU scales with memory). Event-driven from S3, API Gateway, SQS, EventBridge, etc. Watch cold starts & concurrency limits.
  • Lambda facts that show up: default regional concurrency ~1,000 (soft limit); reserved concurrency caps/guarantees a function; provisioned concurrency eliminates cold starts; ephemeral /tmp storage; to reach resources in a VPC (e.g. RDS) attach the function to the VPC — and use RDS Proxy to avoid exhausting DB connections.
  • AWS Fargate — serverless compute for containers (ECS/EKS); no EC2 to manage.
  • Serverless data stores that pair well: DynamoDB, S3, Aurora Serverless.

Containers

ServiceUse
Amazon ECSAWS-native container orchestration. Launch on EC2 (you manage hosts) or Fargate (serverless).
Amazon EKSManaged Kubernetes — choose when you need/​know K8s or portability.
Amazon ECRPrivate container image registry.
App Runner / BeanstalkHigher-level PaaS to deploy web apps/containers with less config.

5.3 · High Availability & Fault Tolerance

  • Eliminate single points of failure: multiple AZs, ASG across AZs behind an ELB, Multi-AZ databases.
  • Elastic Load Balancing distributes traffic and runs health checks; deregisters unhealthy targets. See §6.4 for ALB/NLB/GWLB differences.
  • Amazon Route 53 health checks + failover routing reroute traffic when a region/endpoint is unhealthy. Health checks can monitor endpoints, other health checks (calculated), or CloudWatch alarms.
  • RDS Multi-AZ — synchronous standby in another AZ; automatic failover, typically ~1–2 minutes (HA, not read scaling — the standby serves no reads). Read replicas — async, for read scaling (can be cross-region), and can be promoted to standalone DBs in DR.
  • RDS operations: automated backups enable point-in-time restore (retention 0–35 days, transaction logs every 5 min); manual snapshots persist until deleted; encryption must be chosen at creation — to encrypt an existing DB, snapshot → copy the snapshot with encryption → restore.
  • Aurora — 6 copies of data across 3 AZs, self-healing storage, up to 15 low-lag read replicas, automatic failover (a replica is promoted, typically <30s). Aurora Global Database — cross-region storage-level replication with ~1s typical lag; secondary regions promote in about a minute — the "global relational DB with fast regional DR" answer.
  • S3 — 99.999999999% (11 nines) durability, stored across ≥3 AZs (except One Zone-IA). EFS is multi-AZ; EBS is single-AZ (snapshot to S3 for durability).
  • Immutable infrastructure — replace rather than patch instances (via ASG + new launch template/AMI) for consistency & easy rollback.
HA vs Fault-tolerant Highly available = minimal downtime, quick recovery (e.g. Multi-AZ with brief failover). Fault-tolerant = keeps running with zero interruption despite component failure (e.g. Aurora, or N+1 redundancy). Fault tolerance usually costs more.

5.4 · Disaster Recovery

Two metrics drive the choice: RPO (Recovery Point Objective = acceptable data loss) and RTO (Recovery Time Objective = acceptable downtime). Lower RPO/RTO → higher cost.

StrategyRTO/RPOCostHow it works
Backup & RestoreHours$Back up data (snapshots, S3, AWS Backup); restore into a region on disaster. Cheapest, slowest.
Pilot Light10s of min$$Core (e.g. replicated DB) always on but minimal; spin up the rest on failover.
Warm StandbyMinutes$$$Scaled-down but fully functional copy always running; scale it up on failover.
Multi-Site Active/ActiveNear-zero$$$$Full production in 2+ regions serving traffic; failover is instant. Lowest RTO/RPO.
  • AWS Backup — centralized, policy-based backups across services (EBS, RDS, DynamoDB, EFS, etc.) with cross-region/cross-account copy.
  • S3 Cross-Region Replication (CRR) and DynamoDB Global Tables support active-active data.
  • Elastic Disaster Recovery (DRS) replicates servers for fast recovery.
  • AWS Backup Vault Lock makes backups immutable (WORM) — the answer to "protect backups from ransomware / accidental deletion."

5.5 · Monitoring, Auditing & Infrastructure as Code

These management services thread through every domain and are constantly tested as "which tool answers this question?"

ServiceAnswers the question…Key facts
Amazon CloudWatch"How is it performing?" (metrics, logs, alarms)EC2 basic metrics every 5 min free; detailed monitoring = 1 min ($). Memory & disk-space are NOT default metrics — they need the CloudWatch agent (custom metrics). Alarms trigger SNS/Auto Scaling/EC2 actions. CloudWatch Logs centralizes app/system logs; metric filters turn log patterns into alarms.
AWS CloudTrail"Who did what, when?" (API audit)Records every API call (console, CLI, SDK). 90-day event history by default; create a trail to S3 for long-term retention; log-file integrity validation; data events (S3 object-level, Lambda invoke) cost extra and are off by default.
AWS Config"What changed, and is it compliant?"Records resource configuration history; Config Rules evaluate compliance (e.g. "EBS volumes must be encrypted") and can auto-remediate via SSM. Not a permissions tool — a compliance/inventory tool.
AWS X-Ray"Where is the latency in my distributed app?"Distributed tracing across microservices/Lambda/API GW — service map + per-request traces.
Amazon EventBridge"React when something happens"Route AWS/SaaS/custom events to targets; cron/rate schedules for periodic jobs.
AWS Trusted Advisor"What am I doing wrong overall?"Best-practice checks across cost, performance, security, fault tolerance, service limits. Full checks need Business/Enterprise support.

Infrastructure as Code & ops tooling

  • AWS CloudFormation — declarative templates (JSON/YAML) that create/update/delete resources as a stack. Repeatable environments across accounts/regions (StackSets); drift detection spots manual changes; deleting a stack cleans up everything. The default answer to "provision infrastructure repeatably / avoid manual console changes."
  • AWS Systems Manager (SSM) — fleet ops: Session Manager (shell without SSH/bastion), Patch Manager, Run Command, Parameter Store. Requires the SSM agent + instance role.
  • AWS Elastic Beanstalk — PaaS: upload code, it provisions ELB/ASG/EC2 for you; you keep full control of the underlying resources. "Deploy a web app quickly without managing infrastructure (but still on EC2)."
Classic discriminator CloudWatch = performance/metrics/logs · CloudTrail = API audit ("who deleted the bucket?") · Config = configuration state & compliance ("was this SG ever open to 0.0.0.0/0?") · X-Ray = request tracing · Inspector = vulnerabilities. Exam questions hinge on picking the right one.

↑ back to top

6 · Domain 3 — Design High-Performing Architectures 24%

Five task statements covering performant & scalable storage, compute, databases, networking, and data ingestion/transformation.

6.1 · Storage

Storage types

TypeServiceUse when
ObjectAmazon S3Web assets, backups, data lakes, static hosting, unstructured data at any scale.
BlockAmazon EBSLow-latency disk for a single EC2 instance (boot volumes, databases).
FileAmazon EFS / FSxShared file system mounted by many instances (NFS/SMB).

Amazon S3 essentials

  • 11 nines durability, virtually unlimited. Object size 0 B–5 TB (multipart upload for >100 MB; required >5 GB).
  • Security: Block Public Access (on by default), bucket policies, ACLs (legacy), presigned URLs for temporary access, encryption (SSE-S3/SSE-KMS/SSE-C).
  • Versioning protects against overwrite/delete; MFA Delete adds protection. S3 Object Lock = WORM for compliance.
  • Performance: 3,500 PUT / 5,500 GET requests per second per prefix; parallelize across prefixes. S3 Transfer Acceleration uses edge locations for fast long-distance uploads. Multipart for large objects.
  • Replication: CRR (cross-region — DR, compliance, latency) and SRR (same-region — log aggregation, prod/test copies). Both require versioning enabled on source and destination; existing objects need Batch Replication (new objects only by default).
  • Event notifications — S3 can trigger Lambda, SQS, SNS, or EventBridge on object events (the classic "process every uploaded image" pattern).
  • Static website hosting — host a static site from a bucket; pair with CloudFront + OAC for HTTPS, caching, and keeping the bucket private.
  • S3 storage classes — see §7.1 for the full cost/retrieval table.

Amazon EBS volume types

VolumeTypeBest for
gp3 / gp2SSD (general purpose)Most workloads; boot volumes. gp3 lets you provision IOPS/throughput independently of size.
io2 / io1 / io2 Block ExpressSSD (provisioned IOPS)I/O-intensive, latency-sensitive DBs; highest IOPS & durability; supports Multi-Attach.
st1HDD (throughput optimized)Big sequential workloads: big data, log processing, data warehouses.
sc1HDD (cold)Infrequently accessed, lowest cost block storage.

EBS volumes are AZ-locked; snapshots are incremental, stored in S3, and can be copied across regions (that's how you "move" a volume). Automate snapshot schedules with Data Lifecycle Manager or AWS Backup. Encrypt at creation — encrypting an existing volume means snapshot → copy-encrypted → restore. Instance store = ephemeral local disk (lost on stop/terminate) for very high IOPS scratch data.

Shared file systems

  • Amazon EFS — elastic NFS for Linux, multi-AZ, scales automatically, pay per use; mounts to thousands of instances concurrently (and Lambda). Lifecycle to EFS-IA cuts cost ~90% for cold files; One Zone classes are cheaper still. Performance modes (General Purpose vs Max I/O) and throughput modes (Elastic/Bursting/Provisioned).
  • Amazon FSx — Windows File Server (SMB + Active Directory — the answer for Windows shared drives; Multi-AZ option), Lustre (HPC/ML scratch at GB/s; can present S3 data as a file system), NetApp ONTAP (multi-protocol NFS/SMB/iSCSI), OpenZFS.

Hybrid storage & moving data

ServiceUse for
Storage Gateway — S3 File GatewayOn-prem apps write NFS/SMB → objects land in S3, with a local cache for hot data. "Extend on-prem file storage to the cloud."
Storage Gateway — Volume GatewayiSCSI block volumes: Cached (primary data in S3, cache on-prem) vs Stored (primary on-prem, async snapshots to S3).
Storage Gateway — Tape GatewayVirtual tape library — replace physical backup tapes; archives to Glacier.
AWS DataSyncFast online transfer/sync (NFS/SMB/HDFS/S3 API ↔ S3/EFS/FSx) with scheduling, bandwidth throttling & verification — the "migrate/sync file data over the network" answer.
AWS Snow FamilyOffline bulk transfer — Snowball Edge (~80 TB usable each) shipped to you. Choose when data volume ÷ bandwidth = weeks (rule of thumb: ≥ tens of TB on a constrained link).
AWS Transfer FamilyManaged SFTP/FTPS/FTP/AS2 endpoints backed by S3 or EFS — keep legacy file-transfer clients working, unchanged.

6.2 · Compute

  • EC2 instance families — General purpose (M, T-burstable), Compute optimized (C), Memory optimized (R, X), Storage optimized (I, D), Accelerated/GPU (P, G, Inf). Match the family to the bottleneck.
  • Placement groups — Cluster (low latency, single AZ, HPC), Spread (max 7/AZ on distinct hardware, critical instances), Partition (large distributed systems like HDFS/Cassandra).
  • Auto Scaling + ELB for elastic horizontal scaling (see §5.2).
  • AWS Lambda for event-driven/serverless; right-size memory (also sets CPU). Fargate for serverless containers.
  • AWS Batch for batch jobs; Amazon EMR for big-data frameworks (Spark/Hadoop); Elastic Beanstalk to deploy apps with managed provisioning.
  • EC2 networking bits: an Elastic IP is a static public IPv4 you keep across stop/start (a normal public IP changes); an ENI is a virtual NIC you can detach and move between instances in the same AZ; enhanced networking (ENA) gives high throughput/low jitter for network-bound workloads.
  • AMIs are regional — copy an AMI to another region to launch there (the standard "golden image" multi-region pattern with ASG launch templates).
  • EC2 hibernation preserves RAM to EBS — fast resume for long-boot instances; you pay storage, not compute, while hibernated.
Right service Unpredictable/spiky & short tasks → Lambda. Steady long-running → EC2 (with Savings Plans). Containerized microservices, no server mgmt → ECS/EKS on Fargate. Batch/HPC → Batch / EMR.

6.3 · Databases

ServiceModelUse for
Amazon RDSManaged relational (MySQL, PostgreSQL, MariaDB, Oracle, SQL Server)Traditional relational apps needing SQL, joins, transactions. Multi-AZ for HA, read replicas for scale.
Amazon AuroraMySQL/PostgreSQL-compatible, cloud-nativeHigh performance & availability at scale; 6-way replicated storage; Serverless v2 for variable load.
Amazon DynamoDBServerless key-value / document NoSQLMassive scale, single-digit-ms latency, unpredictable traffic. On-demand or provisioned capacity; Global Tables; DAX cache; Streams.
Amazon ElastiCacheIn-memory (Redis / Memcached)Caching, sessions, leaderboards; reduce DB read load. Redis adds persistence/replication.
Amazon RedshiftColumnar data warehouse (OLAP)Analytics over large datasets, complex queries/BI.
DocumentDB / Neptune / Keyspaces / Timestream / QLDBDocument / Graph / Cassandra / Time-series / LedgerPurpose-built: MongoDB-compatible, graph relationships, wide-column, time-series, immutable ledger.

Performance levers

  • Read replicas offload reads (RDS/Aurora). Multi-AZ is for availability, not scaling.
  • Caching: ElastiCache in front of DBs, DynamoDB DAX for microsecond reads, CloudFront for content.
  • RDS Proxy pools connections — great for Lambda/serverless hitting relational DBs.
  • Choose SQL vs NoSQL by access pattern: relational/joins/ACID → RDS/Aurora; high-scale key lookups & flexible schema → DynamoDB.

DynamoDB specifics that get tested

  • Item size limit 400 KB — store large blobs in S3, keep a pointer in the table.
  • On-demand capacity for unpredictable traffic; provisioned (+ auto scaling) is cheaper for steady load. Choose a high-cardinality partition key to avoid hot partitions.
  • Global Tables — multi-region, multi-active replication (read and write anywhere). Streams capture item-level changes (→ Lambda triggers). TTL deletes expired items at no cost.
  • GSI (query on alternate keys) vs LSI (same partition key, alternate sort key — must be created at table creation).

ElastiCache: Redis vs Memcached

RedisMemcached
Replication + Multi-AZ failover, persistence/snapshots, pub/sub, sorted sets (leaderboards)Simplest possible cache — multithreaded, no persistence, no replication
Default pick when the question mentions durability, HA, or data structuresPick when the question stresses "simplest / multithreaded / no persistence needed"

Migrating databases

  • AWS DMS (Database Migration Service) migrates with minimal downtime — the source stays live (supports full load + ongoing change data capture).
  • Homogeneous (Oracle→Oracle): DMS alone. Heterogeneous (Oracle→Aurora PostgreSQL): use SCT (Schema Conversion Tool) first to convert the schema, then DMS to move the data.
Trap "Improve read performance / reduce read load" → read replica or ElastiCache, NOT Multi-AZ. "Survive an AZ outage" → Multi-AZ. "Microsecond reads for DynamoDB" → DAX, not ElastiCache.

6.4 · Networking

Load balancers

LBLayerUse for
Application (ALB)7 (HTTP/S)Web apps; host/path routing, WebSockets, redirects, auth; targets = EC2/IP/Lambda/containers.
Network (NLB)4 (TCP/UDP/TLS)Extreme performance, millions of req/s, ultra-low latency, static/Elastic IP, TCP/UDP.
Gateway (GWLB)3Deploy/scale third-party virtual appliances (firewalls, IDS/IPS).

Edge & DNS

  • Amazon CloudFront — CDN caching content at edge locations; supports dynamic + static, OAC to lock S3 origins, signed URLs/cookies, Lambda@Edge / CloudFront Functions, WAF integration, DDoS mitigation. Also: origin failover (primary + secondary origin in an origin group) and geo restriction (allow/block countries).
  • Hybrid DNS: Route 53 Resolver endpoints — inbound lets on-prem resolve VPC names; outbound + forwarding rules lets VPCs resolve on-prem domains. The answer to "DNS between datacenter and VPC."
  • AWS Global Accelerator — anycast static IPs routing over the AWS backbone to the nearest healthy endpoint; great for TCP/UDP, gaming, non-HTTP, fast regional failover. (CloudFront caches content; Global Accelerator accelerates/routes traffic.)
  • Amazon Route 53 — DNS + health checks. Routing policies: Simple, Weighted, Latency, Failover, Geolocation, Geoproximity, Multivalue answer, IP-based. Alias records point to AWS resources for free.
  • Record types: A/AAAA (name → IPv4/IPv6), CNAME (name → another name; not allowed at the zone apex), Alias (AWS extension — points at ELB/CloudFront/S3/etc., works at the apex, free queries). "Point example.com at an ALB" → Alias, not CNAME.
  • Routing policy signals: A/B or gradual migration by percentage → Weighted · send users to the lowest-latency region → Latency · compliance/content by user country → Geolocation · active-passive DR → Failover (+ health check) · simple client-side load spread → Multivalue.

Hybrid & private connectivity

OptionUse
Site-to-Site VPNEncrypted tunnel over the internet to your VPC. Quick, cheaper, variable performance.
AWS Direct ConnectDedicated private line to AWS — consistent low latency & bandwidth. Weeks to provision; pair with VPN for encryption/backup.
AWS PrivateLink / Interface EndpointsPrivate access to AWS/partner services without internet exposure.
VPC PeeringConnect two VPCs privately (non-transitive).
AWS Transit GatewayHub-and-spoke connecting many VPCs & on-prem — scales past peering mesh. Supports inter-region peering for global networks.
  • Site-to-Site VPN: two tunnels per connection (HA built in), ~1.25 Gbps per tunnel. Fast to set up (hours).
  • Direct Connect is not encrypted by default — run a VPN over it (or MACsec) when the question demands a private and encrypted link. Dedicated 1/10/100 Gbps; hosted connections from ~50 Mbps via partners; takes weeks-to-months to provision, so "need it now" scenarios start with VPN and migrate to DX.
  • VPC peering doesn't scale: it's non-transitive, so N VPCs need a full mesh (N×(N−1)/2 connections) — the moment a question has "dozens of VPCs" or "simplify connectivity," the answer is Transit Gateway.

6.5 · Data Ingestion, Streaming & Analytics

ServiceRole
Amazon Kinesis Data StreamsReal-time streaming ingest (shards); custom consumers; retention 24 h–365 d.
Amazon Data FirehoseNear-real-time delivery to S3/Redshift/OpenSearch/Splunk; auto-scales, can transform. No consumer code.
Amazon MSKManaged Apache Kafka for streaming.
AWS GlueServerless ETL & Data Catalog; transform formats (CSV→Parquet).
Amazon AthenaServerless SQL queries directly over S3 (pay per data scanned). Pairs with Glue Catalog.
AWS Lake FormationBuild & secure data lakes on S3.
Amazon EMRManaged Hadoop/Spark for large-scale processing.
Amazon OpenSearchSearch & log analytics.
Amazon QuickSightBI dashboards & visualization.
AWS DataSyncFast, automated data transfer on-prem ↔ AWS (over network).
  • Kinesis shard math: each shard ingests 1 MB/s or 1,000 records/s and serves 2 MB/s out — scale by adding shards. Firehose needs no shard management at all.
  • Kinesis vs MSK: Kinesis = AWS-native, simplest ops; MSK = managed Apache Kafka — pick it when the scenario already uses Kafka APIs/ecosystem.
  • Athena cost/perf lever: store data compressed, partitioned, and columnar (Parquet/ORC) — Athena bills per data scanned, so converting CSV→Parquet cuts both cost and query time dramatically (use Glue to convert).
  • Glue crawlers scan S3 and auto-populate the Data Catalog tables that Athena/EMR/Redshift Spectrum query. Redshift Spectrum queries S3 data from Redshift without loading it.
  • Amazon AppFlow — no-code SaaS→AWS data transfer (Salesforce → S3/Redshift).
Streaming signals "Deliver streaming data to S3 with no code" → Firehose. "Real-time processing with custom consumers / replay" → Kinesis Data Streams. "Query S3 with SQL, no servers" → Athena. "Serverless ETL" → Glue. "Kafka" → MSK.

↑ back to top

7 · Domain 4 — Design Cost-Optimized Architectures 20%

Four task statements — cost-optimize storage, compute, database, and network — plus the cost-management tooling that spans all of them.

7.1 · Storage Cost Optimization

S3 storage classes

ClassUse / accessRetrieval
S3 StandardFrequent access, hot datams
S3 Intelligent-TieringUnknown/changing access — auto-moves objects between tiers; small monitoring fee, no retrieval feesms
S3 Standard-IAInfrequent but rapid access; multi-AZms (+ retrieval fee)
S3 One Zone-IAInfrequent, re-creatable data; single AZ (cheaper, less durable)ms (+ retrieval fee)
Glacier Instant RetrievalArchive needing millisecond accessms
Glacier Flexible RetrievalArchive, rare accessmin–hours (expedited/standard/bulk)
Glacier Deep ArchiveLowest cost, long-term (7–10 yr)~12–48 h
  • Lifecycle policies auto-transition objects to cheaper tiers and expire them on a schedule (also: abort incomplete multipart uploads, expire old versions).
  • Minimum-duration gotchas (billed even if you delete/transition earlier): Standard-IA & One Zone-IA 30 days; Glacier Instant & Flexible 90 days; Deep Archive 180 days. IA classes also bill a 128 KB minimum object size — lifecycle-ing millions of tiny objects to IA can cost more.
  • Pick Intelligent-Tiering when access patterns are unknown/variable — it avoids retrieval-fee surprises.
  • Requester Pays buckets shift download costs to the downloader — for sharing large datasets.
  • EBS/EFS: use gp3 over gp2 (~20% cheaper + tunable IOPS/throughput); EFS lifecycle to IA; delete unattached volumes & old snapshots; remember unused Elastic IPs are billed.
  • Move data with the cheapest fit: DataSync (online), Snow Family (offline, large/limited-bandwidth), Storage Gateway (hybrid).

7.2 · Compute Cost Optimization — Purchasing Options

OptionDiscountBest for
On-Demand—Short-term, spiky, unpredictable, or dev/test. No commitment.
Savings Plansup to ~72%Commit to $/hour for 1 or 3 yrs. Compute SP (flexible across EC2/Fargate/Lambda & region) or EC2 Instance SP (deeper, family-locked).
Reserved Instancesup to ~72%Steady-state 1/3-yr commitment to specific instance attributes. Standard (max discount) vs Convertible (flexible).
Spot Instancesup to ~90%Fault-tolerant, interruptible, stateless (batch, CI, big data). 2-minute interruption notice.
Dedicated Hosts / InstancespremiumCompliance, licensing (BYOL), isolation.
  • Right-size with Compute Optimizer & CloudWatch; don't over-provision.
  • Prefer serverless/managed (Lambda, Fargate) to pay only for use and drop idle capacity.
  • Auto Scaling to match demand; schedule non-prod to shut down off-hours; use EC2 hibernation where relevant.
Purchasing signal Steady 24/7 baseline → Savings Plans / RIs. Bursty, interruption-tolerant → Spot. Unknown/short-lived → On-Demand. Mix: baseline on RIs/SP + burst on Spot/On-Demand.

7.3 · Database Cost Optimization

  • Use Reserved Instances for steady RDS/Redshift; Aurora Serverless v2 or DynamoDB on-demand for variable/spiky load.
  • Right-size instances, use appropriate storage (gp3), and set backup/snapshot retention policies to avoid runaway storage cost.
  • Offload reads to read replicas/caching instead of a bigger primary.
  • Pick the right engine/type: DynamoDB (serverless, pay-per-request) can be far cheaper than a large always-on RDS for key-value workloads; columnar (Redshift) for analytics; time-series (Timestream) for metrics.

7.4 · Network Cost Optimization

  • Data transfer is a top hidden cost. Same-AZ private-IP traffic is free; cross-AZ & cross-region & internet egress cost money. Keep chatty components in the same AZ where availability allows.
  • VPC endpoints (esp. free Gateway endpoints for S3/DynamoDB) avoid NAT Gateway data-processing charges and internet egress.
  • NAT Gateway costs per hour + per GB — a single shared NAT is cheaper but less HA than one-per-AZ; balance cost vs resilience.
  • CloudFront reduces origin egress cost and improves performance for repeat content — and S3 → CloudFront origin fetches are free, so serving S3 content through CloudFront is usually cheaper than direct S3 egress.
  • Direct Connect can lower data-transfer rates vs internet for large sustained volumes.
  • Data transfer IN from the internet is free; you pay going out and between AZs/regions — architecture questions about "minimize transfer cost" are really asking you to keep traffic private, local, and cached.

7.5 · Cost Management Tools

ToolPurpose
AWS Cost ExplorerVisualize & analyze spend and usage trends; RI/SP recommendations.
AWS BudgetsSet custom cost/usage budgets and alert when thresholds are exceeded/forecast to be.
AWS Cost and Usage Report (CUR)Most granular billing data → S3 for deep analysis (Athena/QuickSight).
Cost Allocation TagsTag resources to break down cost by team/project/env.
AWS Trusted AdvisorChecks across cost, performance, security, fault tolerance, limits (idle resources, underused RIs).
Consolidated Billing (Organizations)One bill for many accounts + volume/RI/SP sharing discounts.

↑ back to top

8 · In-Scope Service Reference (by category)

The official SAA-C03 in-scope list. Focus first on the ★ heavy-hitters that dominate questions.

Compute

EC2 ★, EC2 Auto Scaling ★, Elastic Beanstalk, AWS Batch, Outposts, Wavelength, VMware Cloud on AWS, Serverless Application Repository.

Serverless & Containers

Lambda ★, Fargate ★, ECS ★, EKS, ECR, AppSync, ECS/EKS Anywhere & Distro.

Storage

S3 ★, EBS ★, EFS ★, FSx ★, S3 Glacier, Storage Gateway, AWS Backup.

Database

RDS ★, Aurora ★, DynamoDB ★, ElastiCache ★, Redshift, DocumentDB, Neptune, Keyspaces.

Networking & Content Delivery

VPC ★, Route 53 ★, CloudFront ★, ELB ★, Direct Connect, Site-to-Site VPN, Client VPN, PrivateLink, Transit Gateway, Global Accelerator.

Security, Identity & Compliance

IAM ★, IAM Identity Center, Organizations ★, KMS ★, ACM, Secrets Manager ★, Cognito, WAF ★, Shield, GuardDuty, Inspector, Macie, Detective, Security Hub, Firewall Manager, Network Firewall, CloudHSM, Directory Service, RAM, Artifact, Audit Manager.

Application Integration

SQS ★, SNS ★, EventBridge ★, Step Functions, Amazon MQ, AppFlow, AppSync.

Analytics

Athena ★, Kinesis ★, Data Firehose, Glue ★, EMR, Redshift, Lake Formation, OpenSearch, MSK, QuickSight, Data Exchange.

Management & Governance

CloudWatch ★, CloudFormation ★, CloudTrail ★, Config, Organizations, Control Tower, Systems Manager, Trusted Advisor, Compute Optimizer, Service Catalog, License Manager, Health Dashboard, Well-Architected Tool, Managed Grafana/Prometheus.

Migration & Transfer

DataSync ★, Snow Family ★, DMS, Application Migration Service, Transfer Family.

Cost Management

Cost Explorer, Budgets, Cost & Usage Report, Savings Plans.

Front-End / ML / Media

API Gateway ★, Amplify, Device Farm; Comprehend, Rekognition, Textract, Transcribe, Translate, Polly, Lex, Kendra, SageMaker; Elastic Transcoder, Kinesis Video Streams.

↑ back to top

9 · Decision Guides & "Which Service?" Tables

The exam constantly asks you to choose between similar services. Memorize these discriminators.

Messaging / decoupling

NeedChoose
Buffer work, decouple, retry, one consumer groupSQS (Standard)
Strict order & exactly-onceSQS FIFO
Fan-out one message to many subscribersSNS (often SNS→SQS)
Route events by content, SaaS/AWS events, schedulingEventBridge
Orchestrate multi-step workflow with stateStep Functions
Migrate app using JMS/AMQP/MQTT brokerAmazon MQ

Storage & file

NeedChoose
Object store / data lake / static siteS3
Block disk for one EC2 instanceEBS
Shared POSIX file system, Linux, multi-AZEFS
Windows/SMB shared files with ADFSx for Windows
HPC / ML high-throughput scratch, S3-linkedFSx for Lustre
Archive, cheapest, hours-OK retrievalS3 Glacier Deep Archive
Unknown access patternS3 Intelligent-Tiering
Move PBs offline / poor bandwidthSnow Family
Hybrid on-prem cache to S3Storage Gateway

Databases

NeedChoose
Relational, managed, standard enginesRDS
Relational at scale, high availabilityAurora
Key-value / document, massive scale, serverlessDynamoDB
Sub-ms caching / sessionsElastiCache (Redis)
Microsecond reads for DynamoDBDAX
Analytics / data warehouse (OLAP)Redshift
Graph relationshipsNeptune
MongoDB-compatibleDocumentDB

Networking & edge

NeedChoose
HTTP/HTTPS routing (path/host), web appsALB
Extreme perf, TCP/UDP, static IPNLB
Cache & deliver content globallyCloudFront
Static anycast IP, route TCP/UDP to nearest region, fast failoverGlobal Accelerator
Dedicated private low-latency link on-premDirect Connect
Quick encrypted tunnel over internetSite-to-Site VPN
Private access to a service, no internetPrivateLink / Interface endpoint
Connect many VPCs + on-prem centrallyTransit Gateway

Monitoring & audit by question

Question being askedService
"How is it performing?" — metrics, alarms, logsCloudWatch
"Who made this API call / who deleted it?"CloudTrail
"What changed / is the config compliant?"AWS Config
"Where's the latency across my microservices?"X-Ray
"Check my account against best practices"Trusted Advisor
"Analyze VPC network traffic"VPC Flow Logs

Migration strategies (the 7 Rs)

StrategyMeaning
Rehost ("lift & shift")Move as-is to EC2 — fastest, no code changes (Application Migration Service).
Replatform ("lift, tinker & shift")Minor optimizations — e.g. self-managed MySQL → RDS.
RepurchaseMove to SaaS (drop the app, buy a product).
Refactor / Re-architectRedesign cloud-native (microservices/serverless) — most effort, most benefit.
RelocateMove at the hypervisor level (VMware Cloud on AWS).
Retain / RetireKeep on-prem for now / decommission entirely.

Security service by job

JobService
Block web exploits (SQLi/XSS), rate-limitWAF
DDoS protectionShield (Advanced for big/L7)
Detect threats/anomalies from logsGuardDuty
Scan for software vulnerabilities/CVEsInspector
Find sensitive data (PII) in S3Macie
Rotate DB/API secrets automaticallySecrets Manager
Manage encryption keysKMS (CloudHSM if dedicated/FIPS-L3)
Customer sign-up/sign-in identityCognito

↑ back to top

10 · Recommended Study Materials (Reddit consensus)

Synthesized from 17 real r/AWSCertifications threads (pass write-ups, course-comparison debates, and the community "master resource list"), weighted by upvotes. The consensus is strikingly consistent across years and experience levels. Source links are in the table at the end of this section.

TL;DR consensus stack: one video course (Maarek to pass fast or Cantrill to learn deeply) + Tutorials Dojo / Jon Bonso practice exams drilled in review mode until you're consistently comfortable (~70–80%+), reviewing every wrong answer. Add the AWS Exam Guide, Well-Architected + Reliability/Cost whitepapers, core-service FAQs, and TD cheat sheets; do some hands-on. You need one of each category — not all of them.

1 · Video courses

Two "kings," and the choice is a well-worn Reddit cliché repeated almost verbatim in nearly every thread: "Stephané Maarek to pass, Adrian Cantrill to learn." Both sit tied at #1 — pick by your goal.

CourseProfileReddit view (pros / cons)
#1Adrian Cantrill
learn.cantrill.io · ~70h
The "learn it properly" pick. Theory-before-service teaching, extensive hands-on labs, big student Discord, one-time purchase.+ Deepest coverage; teaches why not just what; "one of the best quality IT courses I've ever taken." – Long/tedious; covers more than the exam; easy to burn out or skip labs.
#1Stephané Maarek
Udemy · ~27h
The "fast, efficient pass" pick. Concise, exam-focused, cheap on Udemy sale. Includes a 50%-off exam voucher.+ Time-efficient, gets you the paper, great for students/juniors. – "Feels like a cheatsheet"; lighter on deep understanding.
FreeAndrew Brown (ExamPro)
freeCodeCamp YouTube
The consensus free video course.+ Completely free, full-length. – "Very unstructured / all over the place."
Neal Davis (Digital Cloud)
Udemy
Legitimate third option, less discussed.Solid but a distant third to Maarek/Cantrill.
Consensus takeaways Cantrill for depth & real skills; Maarek for a fast, cheap, exam-targeted pass. A minority do Cantrill first, then Maarek as a cram/summary (~⅓ the length) — effective but expensive and usually unnecessary ("generally, do NOT do both"). Udemy pricing tip: never pay more than ~$20 — wait for a sale or use the author's own site.
Community says avoid A Cloud Guru and Pluralsight — "used to be leaders but have fallen behind." And ignore bot spam: "Gascelino Rostero's practice exam book" and "SkillCertPro" are repeatedly flagged as astroturf/bot advertising, not genuine recommendations.

2 · Practice exams most important

Near-unanimous #1: Tutorials Dojo (TD) / Jon Bonso practice exams — recommended in ~15 of 17 threads and repeatedly called "the best money I spent on exam prep." ~$15 for the bundle (also on Udemy, same author). One user: "passed ALL my 7 certs" with them.
  • Why it's loved: a "review mode" with detailed per-answer explanations of why each option is right and why the wrong ones are wrong, linked to cheat sheets. Nearly every pass post calls this the killer feature.
  • Difficulty: mirrors the real exam's scenario style but runs ~10% harder — "wouldn't take the real exam until you're comfortably passing them." Content: 7 timed sets + review/topic/final-test modes, ~467 unique questions.
  • Second sources (all legit, less dominant): Stephané Maarek practice tests (Udemy), Neal Davis (Digital Cloud) tests, and the AWS Official Practice Exam (Skill Builder — "nice to have," not essential).
Never use dumps Real exam questions sold as "guaranteed" matches are brain dumps — high risk of failing and a certification ban. Practice exams (TD/Maarek) are original questions and are fine; dumps are not.

3 · Hands-on labs

Recommended at the Associate level (a minority pass without it — and get criticized for it: "you didn't actually learn AWS… making mistakes is how you learn"). Get hands-on via:

  • Cantrill's built-in labs — the most-praised source of practical skill.
  • Tutorials Dojo hands-on labs — "don't skip them; some exam questions map to them (RDS replicas, S3 Object Lock)."
  • Your own AWS Free Tier account — set a billing budget first to avoid surprise charges. Build: a VPC with public/private subnets, EC2 behind an ALB + Auto Scaling Group, a static site on S3 + CloudFront, and an RDS Multi-AZ instance.

4 · Free resources

  • Andrew Brown on freeCodeCamp (YouTube) — flagship free course; ExamPro also gives one free practice exam on sign-up.
  • AWS Skill Builder free tier — official "Exam Prep: SAA-C03" course + 20 free official practice questions. A widely shared cram hack: the paid tier's 7-day free trial unlocks the official practice exam, flashcards, and labs (subscribe, cancel immediately, keep 7 days).
  • AWS Whitepapers & Well-Architected Framework — the WAF pillars, plus the Reliability and Cost Optimization whitepapers specifically.
  • Core-service FAQs — read the S3, EC2, IAM, and RDS FAQs; "AWS docs are the best resource" recurs often.
  • The official AWS Exam Guide PDF — mandatory to know what's in/out of scope.
  • AWS's 20 free sample questions (on the cert page) — a good difficulty gauge.

5 · Notes, cheat sheets & books

  • Tutorials Dojo cheat sheets — the standout review aid, repeatedly credited ("I cannot emphasize enough how much the cheat sheets helped").
  • Hand-written / condensed personal notes — a strongly endorsed technique: build bullet-point profiles for the 5–10 big services (EC2, S3, DynamoDB, RDS, Aurora, Kinesis, Lambda), flashcard the minor ones, then "funnel" everything down into a short final review sheet.
  • Books are generally discouraged — "they get out of date too quickly." (If you must: the official Sybex guide, or Neal Davis / TD ebooks.)

6 · The recommended path & timeline

  1. Pick ONE course and watch it end-to-end, taking notes and doing labs (Cantrill for depth, Maarek for speed, Andrew Brown if free).
  2. Read the AWS Exam Guide to lock in scope; add the WAF + Reliability/Cost whitepapers.
  3. Hammer Tutorials Dojo — review mode first (read every explanation), then timed. Review every wrong answer, note why you missed it, and turn gaps into flashcards.
  4. Book when consistently comfortable. Since TD runs ~10% harder, aim for ~70–80%+ — but "there's no magic percentage; some pass having maxed out in the low 60s on TD." Trust understanding over the number.
What the exam is really like 65 scenario questions, ~2 min each, pass = 720/1000. As much a reading-comprehension & endurance test as a knowledge test: two answers are often technically correct and differ by a single qualifier — "MOST cost-effective," "LEAST operational overhead," "MOST resilient." That qualifier picks the winner. Typical study time: 2 weeks (experienced) to ~3 months (thorough, working pro).
Logistics tips Prefer a Pearson VUE test center over at-home proctoring if you can. Get a 50% discount voucher (from passing Cloud Practitioner, or bundled with Maarek's course). Results usually arrive 5–10 hours later via Credly/CertMetrics.

Sources (r/AWSCertifications)

ThreadTopic (upvotes)
1d5kkuwMaster resource list (56)
1bdcrlfPassed in 10 days: Maarek + Quizlet (74)
114inysPassed 800+: Maarek + TD + whitepapers (69)
18tniy1Passed 865: Maarek + Cantrill + TD (44)
16ycgpyPassed: TD video course + labs (37)
10nim6kNon-tech pass: Maarek + TD + cheat sheets (35)
1daimmePassed: WhizLabs / Skill Builder / TD (31)
11xomikCantrill vs Maarek debate (29)
1ajfx2cCantrill vs Maarek debate (28)
128o3duPassed: Cantrill + TD + hands-on (25)
1bcz657Passed: TD + GitHub guide (17)
xrubpbStudy guide: Cantrill + TD (14)
157o7x3TD scores + Maarek / Neal Davis (14)
Also: 1d6jfd1, 17a0j48, 1cbcaqn, 11e44tg — Cantrill/TD combos, TD exam details & "what score to book."

↑ back to top

11 · Full Study Plan (≈6 weeks part-time)

This plan is deliberately built on evidence-based learning science, not just "watch videos and cram." Passive re-watching feels productive but produces weak, short-lived memory. The methods below are what actually move knowledge into long-term memory — which is the point of a cert you'll use on the job, not just pass.

The learning principles this plan uses

PrincipleWhy it worksHow to apply it to SAA
Active recall (retrieval practice)Retrieving an answer from memory strengthens it far more than re-reading. The single highest-leverage technique.After each topic, close the notes and write/say everything you remember. Use flashcards & practice questions instead of re-watching.
Spaced repetition (distributed practice)Reviewing at growing intervals beats massed cramming and fights the forgetting curve.Review a topic at day 1, 3, 7, then weekly. Use Anki (or the TD flashcards) which schedule this for you.
InterleavingMixing topics/question types trains you to choose the right approach — exactly what the exam tests.Don't drill one service in isolation; mix VPC + IAM + S3 + DB questions together, like the real exam.
Elaboration & the Feynman techniqueExplaining why in plain language exposes gaps and builds durable understanding.After each domain, teach it out loud (or write) as if to a beginner. Where you stumble = what to restudy.
Dual codingPairing words with visuals improves recall.Sketch architecture diagrams (VPC, Multi-AZ, DR patterns) from memory rather than copying them.
Concrete practice & testing effectDoing beats watching; being tested is itself a learning event.Build in a free-tier account; take practice exams early and often (not only at the end).
Sleep & spacing over crammingMemory consolidates during sleep; short daily sessions beat marathon weekends.Study ~45–60 min most days > one 6-hour Sunday. Never pull an all-nighter before the exam.

The weekly plan

Assumes ~1 hr/weekday + a longer weekend block. Compress to ~3 weeks if experienced, or stretch to 8–10 for a gentler pace — the structure matters more than the exact weeks. Each week ends by testing, not by finishing videos.

PhaseFocusActions (learn → retrieve → apply)
Week 1–2
Foundations
Global infra, IAM, VPC, EC2, S3Learn: first half of your video course. Retrieve: after each section, blank-page recall + make flashcards. Apply: build a VPC with public/private subnets, an EC2, an S3 bucket, IAM users/roles. End week 2 with a short quiz on weeks 1–2.
Week 3
Core services
Databases, ELB/ASG, decouplingLearn: finish the course. Apply: build an ALB + Auto Scaling Group, RDS Multi-AZ, an SQS→Lambda flow. Retrieve: daily 10-min flashcard review of all prior weeks (spacing), not just new material.
Week 4
Depth & breadth
Security & cost (Domains 1 & 4), DR, edge, dataStudy the highest-weight/trickiest domains deeply. Read the WAF pillars. Feynman: explain each domain out loud. Draw DR strategies & a 3-tier architecture from memory. Start interleaved topic quizzes.
Week 5
Practice
Full practice exams in review modeTake Tutorials Dojo sets. For every question (right or wrong) read the explanation and write one line on why the wrong options are wrong. Turn each miss into a flashcard. Re-study weak areas the next day (spacing).
Week 6
Polish
Consistency, gaps, taperRetake fresh sets until consistent 80%+. Do the free official AWS practice questions. Skim S3/EC2/VPC/RDS FAQs for edge cases. Final 2 days: light flashcard review only, sleep well, don't cram new material. Skim the Cram Jam the morning of.

A repeatable daily routine

  1. 5–10 min warm-up: flashcard review of older material (spaced recall) before anything new.
  2. 30–40 min new learning: one focused topic — video/reading in short chunks.
  3. 10–15 min retrieval: close everything, brain-dump what you learned, then check & correct.
  4. Weekend: a timed, interleaved practice set + review; sketch one architecture from memory.
Readiness bar You're ready when you consistently score ≥80% on fresh practice sets and can explain why each wrong option is wrong and teach any domain from a blank page — recognition ≠ recall. That gap is exactly what active recall closes.
Retention after the exam To keep the knowledge (not just pass): space a few review sessions in the weeks after the exam, and apply it — build something real, or use it at work. Skills used are skills kept.

↑ back to top

12 · Exam-Day Tips & Common Traps

Technique

  • Read the last sentence first. Identify what's actually optimized for: cost, least operational overhead, highest availability, lowest latency, most secure. The "best" answer changes with that keyword.
  • Eliminate distractors. Usually 2 options are clearly wrong; decide between the last 2 on the optimization keyword.
  • "Least operational overhead / managed" → favor serverless/managed (Lambda, Fargate, Aurora Serverless, S3, managed services) over self-managed EC2.
  • Flag & move on. 130 min / 65 Q ≈ 2 min each. Don't sink 8 minutes on one — flag it, keep pace, return later.
  • Never leave blanks — no penalty for guessing.

Recurring traps

  • Multi-AZ ≠ read scaling. Multi-AZ = availability; read replicas/caching = read performance.
  • Security Group vs NACL: SG stateful/allow-only/instance; NACL stateless/allow+deny/subnet.
  • Gateway endpoint (S3/DynamoDB, free) vs Interface endpoint (PrivateLink, ENI, paid).
  • CloudFront (cache content) vs Global Accelerator (route/accelerate traffic, static IPs).
  • SCPs don't grant permissions — they cap them. You still need IAM allows.
  • Spot only for interruption-tolerant workloads; not for a stateful primary DB.
  • KMS for managed keys; CloudHSM only when "dedicated/single-tenant/FIPS 140-2 Level 3."
  • EBS is single-AZ; use snapshots (to S3) or EFS for multi-AZ/shared.
  • Kinesis Data Streams (custom real-time consumers/replay) vs Firehose (no-code delivery to stores).
Keyword → intent "decouple/buffer" = SQS · "notify many" = SNS · "highly available" = Multi-AZ/multi-AZ ASG · "durable/archive" = S3/Glacier · "cheapest transfer of PBs" = Snow · "no servers to manage" = serverless · "cross-account guardrails" = SCP · "temporary credentials" = IAM role/STS.

↑ back to top