38 exam-focused study guides covering the entire SAA-C03 syllabus — written the way a good teacher explains, not the way documentation reads.
Battle-tested on a successful exam attempt — shared in the hope they help you pass too. 🎉
Every guide follows the same battle-tested format:
- The idea — each service explained from zero with a real-world analogy (Multi-AZ = a spare tire, Read Replicas = extra checkout lanes, Route 53 = a phonebook, NAT = a receptionist mailing your letters…)
- Core concepts — the exam-tested facts and numbers, with explicit "THE trap" callouts for the mistakes the exam is designed to harvest
- Question patterns — realistic exam-style scenarios with the answer and the signal keywords that crack them
- Pocket card — a keyword → answer table for rapid review
The guides teach the decision patterns the exam actually tests ("Multi-AZ vs Read Replica", "Gateway vs Interface Endpoint", "SQS vs SNS vs Kinesis vs EventBridge") — not service trivia in isolation.
📖 Topic Guides Index — all 38 guides with a suggested reading order grouped by exam weight.
The heavy hitters, if you're short on time:
- VPC — the single biggest exam topic
- S3 — storage classes, encryption, the works
- RDS & Aurora — home of the most-tested distinction on the exam
- SQS, SNS & Kinesis — the messaging block
- Exam Traps & Key Patterns — ⭐ read this last, and again on exam morning
- Read the last sentence of the question first — "MOST cost-effective" vs "LEAST operational overhead" vs "highly available" decides between the two plausible finalists.
- Count the requirements — "X as well as Y" is a checklist; the right answer ticks every box. Half-solutions are planted for people who stop at the first match.
- Scan options for poison qualifiers — serverless, automatically, at no cost, immediately, directly, cannot/always — a true fact welded to one false word is the exam's favorite distractor.
- When two options are twins, the entire question lives in the differing clause.
- Requirements are eliminators, not decoration — a stated number (retrieval time, IOPS, RPO/RTO) exists to kill specific options. Eliminate first, then pick the cheapest/most-managed survivor.
- When every familiar option is wrong-scope, the unfamiliar one is the answer — real-but-unknown features sound specific and boring; fabricated ones sound grand and vague.
Community study notes — not affiliated with or endorsed by AWS. Accurate to the SAA-C03 exam as of mid-2026; always cross-check details that matter against current AWS documentation.
CC BY 4.0 — you're free to use, share, and adapt these guides, but you must give credit: mention RonitSachdev and link back to this repository in anything you build from them. If these helped you pass, a ⭐ on the repo is appreciated too.