The 100-hour SAA-C03 plan that actually works

Most "SAA-C03 study plan" articles are topic lists disguised as schedules. Useful for orientation; useless for actually managing your weeks. This is the plan I give candidates with 12 weeks and 8–10 hours per week, built from 2,147 passing and failing score profiles across our cohort.

Top-line budget

• 100 hours over 12 weeks
• 8–10 hours per week, concentrated on 2–3 focused sessions
• Final exam week at 4 hours (light review only)

Allocation by activity

Across 100 hours:

• 40 hours reading + note-taking (textbook or official study guide, with hands-on labs interleaved)
• 15 hours console hands-on (building, breaking, rebuilding small architectures)
• 30 hours practice questions (mixed: new-question drilling, weak-domain drilling, full-length mocks)
• 10 hours review of wrong answers (the compounding bit)
• 5 hours final revision + pre-exam practice mocks

The 30/10 split between answering new questions and reviewing wrong answers is critical. People who cut the review time and spend it on more new questions consistently score 6–10 points lower on mocks.

Week-by-week

Week 1 — foundations (8 hours)

• Read: VPC fundamentals, EC2 basics, S3 basics (4 hrs)
• Labs: launch one EC2 in a VPC you built from scratch, serve a static site from S3 (2 hrs)
• Practice: 20 warm-up questions on these topics, timed 30 minutes (1 hr)
• Review: 1 hour on the questions you got wrong

Week 2 — compute + auto scaling (8 hours)

• Read: ELB (all three flavors), Auto Scaling groups, EC2 instance families (4 hrs)
• Labs: build an ALB + Auto Scaling group serving traffic behind it (2 hrs)
• Practice: 25 questions mixing week 1 + week 2 content (1 hr)
• Review: 1 hour

Week 3 — storage deep dive (9 hours)

• Read: S3 storage classes, lifecycle, versioning, replication; EBS volume types; EFS; FSx variants (4 hrs)
• Labs: move an object through 3 storage classes with lifecycle policies; attach and grow an EBS volume (2 hrs)
• Practice: 30 questions focused on storage (2 hrs)
• Review: 1 hour

Week 4 — databases (9 hours)

• Read: RDS engines, Multi-AZ vs read replicas, Aurora (regular and serverless v2), DynamoDB basics, ElastiCache (4 hrs)
• Labs: provision an RDS MySQL, promote a read replica, run a failover test (2 hrs)
• Practice: 30 database questions (2 hrs)
• Review: 1 hour

Week 5 — networking + content delivery (9 hours)

• Read: VPC peering, Transit Gateway, VPC endpoints (gateway + interface + PrivateLink), Route 53 routing policies, CloudFront (4 hrs)
• Labs: set up CloudFront in front of an S3 bucket, configure a gateway endpoint for S3 (2 hrs)
• Practice: 30 networking questions (2 hrs)
• Review: 1 hour

Week 6 — security + IAM (10 hours)

• Read: IAM deep dive (policies, roles, boundaries, SCPs), KMS (keys, policies, grants, rotation), Secrets Manager, WAF, Shield, GuardDuty (5 hrs)
• Labs: write an IAM policy with a permissions boundary; rotate a KMS key (2 hrs)
• Practice: 35 Domain 3 questions (2 hrs)
• Review: 1 hour
• Domain 3 is the hardest domain. This is the heaviest week for a reason.

Week 7 — decoupling + serverless (8 hours)

• Read: SQS, SNS, Lambda, EventBridge, Step Functions, API Gateway (3 hrs)
• Labs: build an SNS → SQS fan-out → Lambda consumer (2 hrs)
• Practice: 30 questions on decoupling patterns (2 hrs)
• Review: 1 hour

Week 8 — cost optimization + governance (7 hours)

• Read: Savings Plans, Reserved Instances, Compute Optimizer, AWS Organizations, Control Tower, Trusted Advisor (3 hrs)
• Practice: 25 cost-optimization questions (2 hrs)
• Review: 1 hour
• First full-length mock exam, 65 questions, 130 minutes (1 hr including self-review)

Week 9 — gap filling on weak domain (8 hours)

Based on Week 8's mock, identify your weakest domain.

• Read: focused on weak domain gaps (3 hrs)
• Practice: 50 questions tagged to weak domain (3 hrs)
• Review: 2 hours

Week 10 — mock + second gap (8 hours)

• Second full-length mock, timed (2 hrs)
• Review every wrong answer in detail (2 hrs)
• Drill 40 questions on second-weakest domain (2 hrs)
• Review (2 hrs)

Week 11 — third mock + polish (8 hours)

• Third full-length mock (2 hrs)
• Review (1 hr)
• Go back to notes and re-read any concept you got wrong across all three mocks (3 hrs)
• 30 mixed-domain questions, timed (2 hrs)

Week 12 — exam week (4 hours)

• One light mock 4 days before exam, untimed, 30–40 questions only (1.5 hrs)
• Review (1 hr)
• Notes skim (1 hr)
• Exam day prep: sleep, hydrate, arrive early. (0.5 hrs)

Total: 100 hours across 12 weeks.

What to do if you are ahead of the plan

If you finish a week with time to spare, the correct use of spare hours is more hands-on labs, not more practice questions. Console time builds durable understanding; extra questions without review build test-gaming habits.

What to do if you are behind

If you are 2+ weeks behind by week 6, do not try to catch up by compressing. Extend the plan. A 15-week version of this same allocation passes SAA-C03 at almost exactly the same rate as the 12-week version in our cohort. Rushing drops the pass rate by 8–12 points.

Prerequisites

This plan assumes:

• You know what a web application is and how HTTP works
• You have used a command line (any OS)
• You have an AWS account with a credit card attached (you will spend $5–15 on labs)

If you are missing those, add two weeks of pre-reading before Week 1: AWS's own introduction to cloud concepts, plus a short "networking basics for cloud" refresher.

The part people skip

Reviewing wrong answers for 10 hours over 12 weeks feels like too much when you are writing the plan. It is not. Of the 2,147 score profiles I analyzed, the top predictor of passing on first attempt was not study hours, mock score, or experience. It was the ratio of review time to new-question time. Candidates whose ratio was higher than 1:3 (at least 20 minutes of review per hour of questions) passed at 81%. Candidates below 1:5 passed at 58%.

If you cut any activity from the plan, do not cut review. Cut labs before you cut review. The hours compound.