AWS Solutions Architect Associate: A 4-Week Study Plan

The SAA-C03 is a well-bounded exam, which means four weeks at 10–12 hours a week is a realistic target for someone with some hands-on AWS exposure. The reason people fail it is not lack of content coverage — it is that the exam asks which of four working solutions is the cheapest or most resilient, and that distinction only comes from practice questions, not from watching a course. Budget accordingly.

If you would rather not build this by hand, CramCal does the arithmetic for you: type in your exam date and your topic list, and it lays the whole thing out day by day with the review dates already spaced. It runs in the browser, there is no signup, and the first week of the plan is free to look at.

The four-week breakdown

• Week 1 — IAM, VPC, EC2. Networking is the spine of the exam and the thing most people are weakest on. Subnets, route tables, NAT gateways versus NAT instances, security groups versus NACLs, VPC peering versus Transit Gateway. Build one VPC by hand in the console — it is worth the hours.
• Week 2 — Storage and databases. S3 storage classes and lifecycle policies, EBS volume types, EFS versus FSx, RDS versus Aurora versus DynamoDB. The exam loves cost-optimisation questions here, so learn the price ordering of the storage classes, not just their names. Week 1 topics hit day-7 review.
• Week 3 — High availability, decoupling, and security. Auto Scaling, load balancer types and when each applies, SQS versus SNS versus EventBridge, CloudFront, Route 53 routing policies, KMS. Start doing full practice exams this week, not next.
• Week 4 — Practice exams and gap repair. One full practice exam every other day, with a full day of review after each. Do not chase a passing percentage on practice tests; chase understanding why each distractor is wrong. Week 1 and 2 topics hit their day-30 reviews here, which is exactly when you want them back.

Three weeks of content and one week of practice is the minimum practice ratio. If you have five weeks, add the extra week to practice, not to content — the marginal hour of practice questions is worth several marginal hours of video.

The spacing intervals that do the work

The single highest-leverage thing in any study schedule is when you revisit a topic, not how long you sat with it the first time. The interval pattern that survives contact with a real calendar is:

• Day 0 — first pass. Read, work problems, take notes. Expect to feel like you know it. You do not yet.
• Day 1 — first review. Short, 10–15 minutes. This is the review that stops the 24-hour cliff.
• Day 3 — second review. Do problems, not re-reading. Re-reading feels productive and is not.
• Day 7 — third review. By now you should be able to reconstruct the topic from a blank page.
• Day 14 — fourth review. Mixed in with other topics, not blocked.
• Day 30 — final review, or the nearest date before the exam if there is not 30 days left.

Each review is a fraction of the original session — roughly 20% of the initial time. That is what makes the whole thing fit. Six touches on a topic costs about twice a single session, and the retention difference at test time is not subtle.

The reason people do not do this is purely bookkeeping. If you cover 40 topics, you are tracking 240 review dates by hand. That is the arithmetic that kills the plan in week two.

Four ways these plans die

1. Front-loading the hard content. Putting the worst topic in week one feels virtuous and means you review it once and never again. Hard topics need to be early enough to get four review touches, which usually means the first third of the runway — not day one.
2. No slack days. A schedule with seven study days a week has a 100% failure rate, because the first missed day cascades into every subsequent one. Build in one or two empty days per week explicitly labelled as catch-up. They will get used.
3. Re-reading instead of retrieving. If a review session does not involve producing the answer from memory, it is not a review session. Cover the page. Write it out. Then check.
4. Measuring hours instead of topics. Hours logged is a comfort metric. Topics covered and topics reviewed on schedule is the metric that predicts a score.

AWS-specific: when a question gives you four technically correct answers, the deciding word is almost always in the stem — 'most cost-effective', 'least operational overhead', 'highest availability'. Train yourself to find that word first. Half of all misses are from answering a different question than the one asked.

Get this plan built around your actual test date

Every schedule above assumes a clean runway. Yours will not be clean — you have a job, a term, a week you are away. The useful version of a study plan is the one that starts from your date and your topics, not a generic template.

Open CramCal, enter your AWS SAA-C03 date and the topics you need to cover, and it generates the day-by-day schedule with spaced review dates already placed. Free preview of the plan; the full schedule plus a calendar export file (.ics for Google Calendar, Apple Calendar or Outlook) is a one-time $9 unlock. No account, no subscription, nothing stored on a server.

Written by the team behind CramCal, a free study-schedule generator.