Study TimelineSAA-C03AWS · Associate

How Long to Study for AWS SAA-C03?

Most people need 60 to 150 hours — roughly 6 to 10 weeks — depending on how much real cloud experience they bring. Here is the honest timeline by experience level, a week-by-week 8-week plan, and what makes prep faster or slower.

60–150 hrsTotal study time
6–10 wksTypical timeline
12–15 hrsPer week
65 Q / 130 minExam length
720/1000Pass score
How long to study for the AWS SAA-C03 exam timeline by experience level

01 The short answer

Plan for 60–150 hours of focused study, spread across 6–10 weeks. An engineer already working in cloud or DevOps can be ready in around 60–80 hours. Someone new to cloud entirely usually needs 130–150+ hours. At a sustainable 12–15 hours per week, the middle of that range lands almost everyone at a 6–10 week plan.

SAA-C03 is not a vocabulary test, and that is exactly why raw hours matter less than how you spend them. The exam is 65 questions in 130 minutes — multiple-choice and multiple-response — and almost every item is a scenario that asks you to pick the best architecture for a given goal: secure, resilient, high-performing, or cost-optimised. Reading the docs tells you what a service does; only practice teaches you to choose between two services that both “work” when one is cheaper, more durable, or better fitted to the constraint. So scenario practice eats more of your hours than reading ever should.

Know what you are being scored on. SAA-C03 is graded on a scaled 100–1000 range with a pass mark of 720. Of the 65 questions, 50 are scored and 15 are unscored trial items, and the model is compensatory — you only need to pass overall, not each domain. AWS recommends candidates have roughly one year of hands-on experience designing AWS solutions, so factor real console time into your plan rather than treating it as pure book study.

02 How long it takes by experience level

Your starting point matters more than any other factor. Find the lane that sounds most like you — the bar shows roughly how much ground you have to cover.

Working in cloud / DevOps

60–80 hrs

You already deploy on AWS or a similar cloud, understand IAM, VPCs, and managed services, and just need to map that experience onto SAA-C03’s well-architected framing and the four scored domains.

Pace: ~4–6 weeks at 12–15 hrs/week

IT background, new to AWS

90–120 hrs

You know networking, servers, and storage from an on-prem or sysadmin role, but AWS service names, the shared-responsibility model, and pay-as-you-go cost thinking are new. Most of your time goes on mapping concepts to AWS equivalents.

Pace: ~7–9 weeks at 12–15 hrs/week

New to cloud entirely

130–150+ hrs

You are coming from outside infrastructure, or this is your first technical certification. You need to build cloud fundamentals first — consider sitting CLF-C02 (Cloud Practitioner) before SAA-C03 so the foundations are not new on top of everything else.

Pace: ~10–12 weeks at 12–15 hrs/week
Use a calculator, not a guess. Plug your weekly availability into the study-time calculator to turn an hours estimate into a real finish date before you book.

03 A week-by-week 8-week plan

This is the “IT background, new to AWS” track — the most common starting point. Compress it to 4–6 weeks if you already work in cloud, or stretch it to 10–12 if cloud is brand new. The order matters: get IAM and the security foundations in early, then weight your time toward the two heaviest domains — Secure (30%) and Resilient (26%).

WK
1

Foundations & IAM

Set up a free-tier account, learn the shared-responsibility model, regions and availability zones, and IAM users, roles, and policies. Read the SAA-C03 exam guide and note the four domain weights. Goal: be comfortable navigating the console before any deep study.

~14 hrs
WK
2

Compute & storage

EC2 instance families and pricing models, Auto Scaling, EBS vs instance store, and the S3 storage classes and lifecycle rules. Spin up real resources — an instance, a bucket, a lifecycle policy — rather than only reading about them.

~14 hrs
WK
3

Networking & VPC

VPCs, subnets, route tables, security groups vs NACLs, NAT gateways, and the load balancer family (ALB, NLB, Gateway). Networking trips up the most candidates, so build one VPC by hand end to end.

~15 hrs
WK
4

Databases & resilience (Resilient 26%)

RDS Multi-AZ vs read replicas, Aurora, DynamoDB, and ElastiCache — plus the resilience patterns the exam loves: Multi-AZ failover, cross-region backups, and decoupling with SQS and SNS. This block leans straight into the second-heaviest domain.

~16 hrs
WK
5

Security deep dive (Secure 30%)

The single biggest domain. KMS and encryption at rest and in transit, IAM policy evaluation, S3 bucket policies and Block Public Access, Secrets Manager, WAF, and Shield. Drill 25–30 security scenarios and review every miss.

~16 hrs
WK
6

Performance & cost (High-Performing 24% & Cost 20%)

CloudFront, caching, the right storage and compute for a workload, plus the cost levers: Reserved Instances, Savings Plans, Spot, S3 storage-class choices, and right-sizing. Learn to spot the cheapest option that still meets the requirement.

~14 hrs
WK
7

Full-length mock exams

Sit at least three complete 65-question, timed simulations. Score each domain separately and pour your remaining time into whichever falls below 80%. This is where readiness is actually proven, not assumed.

~14 hrs
WK
8

Final review & book

Light review of weak areas, re-read your notes on the heavy Secure and Resilient domains, rest the day before, and sit the exam. Don’t cram new services in the last 48 hours — protect your recall.

~10 hrs

04 What makes your timeline faster or slower

Two people with identical job titles can need wildly different hours. These are the factors that move the needle most.

▲ Speeds you up

  • You build on AWS day to day and have hands-on console time
  • You already hold CLF-C02 (Cloud Practitioner), so the basics are done
  • Comfortable with networking and Linux from a prior IT role
  • You launch real resources instead of only reading docs
  • You test yourself early instead of waiting until exam week

▼ Slows you down

  • No prior cloud exposure — everything is a new concept
  • VPC networking and IAM policy logic are unfamiliar
  • Studying 30–45 minutes at a time around a full-time job
  • Only watching videos instead of doing labs and questions
  • Memorising service names without learning when to choose each
The most common timeline killer: passive studying. Watching course videos at 1.5x feels productive but barely moves your score. Candidates who shift at least half their hours to hands-on labs and scenario practice finish weeks sooner than those who only watch and read until exam day.

05 A realistic weekly schedule

Most people pass while working full time. The trick is consistency, not heroics — this ~13-hour week is sustainable for the whole 6–10 weeks.

DayTimeFocus
Mon–Thu1.5 hrs (evening)Study one service area, do a short hands-on lab, then answer 20–25 practice questions and review every miss
FridayRestNo study — protect against burnout
Saturday4 hrsOne timed mini-mock (30–40 questions) plus a full review of wrong answers and the why behind each
Sunday3 hrsAttack your weakest domain and build something in the console to cement it
The 85% rule: don’t book the exam until you score a repeatable 85%+ across fresh full-length mocks, with no single domain below 80%. The pass mark is 720/1000, but a steady 85% on quality practice gives you the margin to absorb a few curveball questions on the day.

06 FAQ

How many hours do you need to study for AWS SAA-C03?

Most candidates need 60–150 hours of focused study. Engineers already working in cloud or DevOps can be ready in roughly 60–80 hours; people new to cloud entirely usually need 130–150+ hours. Spread over a typical 12–15 hours per week, that is about 6–10 weeks.

Can you study for the AWS SAA-C03 in one month?

It is realistic for engineers who already use AWS daily and can commit serious hours each week. With around a year of hands-on AWS experience you can be ready in 4–6 weeks. For someone new to cloud studying 1–2 hours an evening, one month is too tight; a 6–8 week plan that weights practice over reading is far safer.

What is the passing score for the AWS SAA-C03 exam?

The SAA-C03 is scored on a scale of 100 to 1000, and you need 720 to pass. The exam is 65 questions in 130 minutes, of which 50 are scored and 15 are unscored. Scoring is compensatory, so you only need to pass overall, not each domain. As a readiness proxy, aim for a repeatable 85%+ on full-length practice exams before you book.

How long before the exam should I take practice tests?

Do light practice questions from week one to learn how SAA-C03 frames scenarios, but reserve the final 1–2 weeks for full-length, timed mock exams. You want at least three complete 65-question simulations under exam conditions, scoring a repeatable 85% or higher, before scheduling the real thing.

ExamCert
ExamCert TeamCertified project & cloud pros helping you pass faster.