AWS SAA-C03 Study Plan: 4 Weeks to Exam-Ready
Four weeks is enough to pass the AWS Solutions Architect Associate (SAA-C03) — if you already have some cloud exposure and you study 10–15 hours a week with a clear plan. If you are a complete beginner, give yourself 6–8 weeks and use this plan at a slower pace: the week-by-week structure still works, just stretched out. The exam is 65 questions in 130 minutes, with a passing score of 720 on a 100–1,000 scaled score, and it tests whether you can design systems on AWS — not whether you can recite service definitions. That means the plan below mixes reading with hands-on practice from day one: the AWS Free Tier lets you build almost everything the exam covers at no cost. Every week links to our free SAA study guides, each with original practice questions and full explanations.
Before Week 1: set up (2–3 hours)
- Create an AWS account and set up billing alerts at $0 and $5 so you are never surprised by a charge. The Free Tier covers the services you need for this plan; set a calendar reminder to delete anything you create.
- Book the exam — or at least pick a date. A fixed date turns "I'll study someday" into a deadline. You can reschedule with Pearson VUE if life intervenes, but a date on the calendar is the single best motivator there is. The exam costs $150.
- Read the exam guide. Our SAA exam details page has the format, the four domain weights, and the booking information. Know what you are preparing for before you start.
- Decide your daily habit. Two hours a day, five days a week, beats a single weekend binge. Short, regular sessions build the kind of durable understanding the exam tests.
Week 1: Identity, networking, and compute (Domains: Secure 30%, Resilient 26%)
Week 1 covers the foundations everything else rests on. Start with IAM — users, roles, policies, and the principle of least privilege — because identity appears in almost every domain. Then VPC: subnets, route tables, security groups versus network ACLs, NAT gateways, and VPC endpoints. VPC is the topic candidates most often under-study, and it is heavily tested. Finish the week with EC2 (instance types, pricing models, placement groups) and load balancers and Auto Scaling, which together form the backbone of resilient architectures.
Hands-on this week: create a VPC with public and private subnets, launch an EC2 instance in the private subnet behind a load balancer, and reach it through a NAT gateway. If you can build that from scratch, you understand the week's material. Questions: do the practice questions in each guide as you finish it, and read every explanation.
Week 2: Storage, databases, and serverless (Domains: Resilient 26%, High-Performing 24%)
Week 2 is the biggest week for service comparisons — the exam's favourite question type. Study S3 (storage classes, lifecycle policies, versioning, encryption) and EBS and EFS, and be able to answer "which storage service?" for any scenario: object vs block vs file, and when each one fits. Then databases: RDS vs DynamoDB vs Aurora vs Redshift, read replicas vs Multi-AZ, and when to cache with ElastiCache. Finish with Lambda and serverless — event-driven design, API Gateway, SQS vs SNS, and Step Functions.
Hands-on this week: build a small serverless flow — an S3 upload that triggers a Lambda function that writes to DynamoDB. It takes an hour and it teaches you more about how the services connect than any amount of reading. Questions: the database and storage comparisons are heavily tested, so do all the practice questions in those guides, and note the comparison tables for revision.
Week 3: Content delivery, monitoring, cost, and security (Domains: High-Performing 24%, Cost-Optimized 20%, Secure 30%)
Week 3 covers the services that make architectures fast, observable, cheap, and safe. Study CloudFront and Route 53 (caching, edge locations, routing policies, and when a CDN is the answer), monitoring (CloudWatch, CloudTrail, and how to detect problems before users do), cost optimisation (right-sizing, Savings Plans vs Reserved Instances, S3 storage classes, and the cost-effectiveness trade-offs the exam loves), and security services (KMS, Secrets Manager, WAF, Shield, and GuardDuty). Finish with migration — the six R's, and how to move workloads to AWS with the least disruption.
Hands-on this week: put CloudFront in front of an S3 website, set up a CloudWatch alarm, and explore the AWS Pricing Calculator for a small architecture. Questions: do the remaining guide questions. By the end of this week you should have covered every guide on the site — if any guide is still unread, it is now your priority.
Week 4: Mock tests, weak spots, and exam technique
Week 4 is not for learning new material — it is for turning knowledge into exam performance. Take the SAA mock test under real exam conditions: 130 minutes, no pausing, no notes. Then study your per-domain score breakdown: whichever domain scored lowest is where your remaining study time goes. Re-read those guides, redo their questions, and take a second mock two or three days later. Two full mocks is the minimum; three is better.
Alongside the mocks, drill exam technique. The SAA's questions turn on qualifier words: "most cost-effective", "with the least operational overhead", "highly available", "with the least latency". Read the requirement before the options, and eliminate the options that violate it — most questions have two options you can rule out quickly, leaving a choice between two plausible designs. Manage your time: 130 minutes for 65 questions is exactly two minutes per question, so check the clock every 15 questions and flag anything that needs more than two minutes. There is no penalty for guessing, so answer every question.
In the final two days, stop learning and start reviewing: re-read your notes, redo the questions you got wrong, and skim the SAA cheat sheet for a final pass over the comparison tables. The day before the exam, stop studying by early evening. A rested brain beats a crammed one.
If you have more (or less) time
Eight weeks: follow the same structure at half pace — two weeks per phase — and add a second hands-on project, such as a three-tier web application with a database, a load balancer, and a CDN. Our SAA study planner lays out 2-week, 4-week, and 8-week schedules. Two weeks: possible only if you already work with AWS daily — skip the hands-on labs, study the guides in domain order, and take a mock test every other day. Complete beginners: add a Week 0 covering the AWS Cloud Practitioner-level basics (what cloud computing is, the global infrastructure, the shared responsibility model) before starting Week 1, and plan on 6–8 weeks total.
What if you fail?
AWS requires a 14-day wait before a retake, and each attempt costs the full $150 — so use the wait well. Your score report shows your performance by domain: treat it as a study plan, revisit the weak domains in the guides, and take another mock before rebooking. There is no limit on the number of attempts, and a fail on the first try with a targeted second attempt is a common path to passing. The certification is valid for three years once you pass, and passing any AWS exam earns you a 50% discount voucher toward your next AWS exam — which many candidates use for their next certification. Start today with the SAA study guides and the mock test: four weeks from now, you could be exam-ready.