The honest answer is somewhere between three weeks and three months, and which end you land on depends almost entirely on two things: which exam you’re taking and how much of this you already know.

Let me give you numbers you can actually plan around.

Timelines by certification

These assume you’re working full time and studying evenings and weekends, roughly 8 to 12 hours a week.

**Cloud Practitioner: 2 to 4 weeks.** If you work in tech already, two weeks is achievable. If cloud is completely new, give it a month. This is a breadth exam, not a depth exam, and most of the work is vocabulary.

**Associate level: 6 to 10 weeks.** Solutions Architect, Developer, SysOps, Data Engineer. Six weeks if you’ve got infrastructure experience, ten if you’re coming in fresh. This is the exam most people ask about, and the most common mistake is budgeting four weeks and then feeling like a failure in week five.

**Professional level: 10 to 16 weeks.** These are genuinely hard, and people who rush them fail them. If you’re already doing the work day to day, the low end is realistic. If not, plan for the high end or reconsider whether you’re ready.

**Specialty: 6 to 12 weeks**, almost entirely dependent on whether the domain is already your job.

What moves you to the fast end

**Existing infrastructure knowledge.** If subnets, routing tables, and firewalls are already familiar, you’ve skipped the hardest part of the associate exams. Networking is where most beginners lose weeks.

**A job that touches AWS.** Even occasional exposure compounds. You’ve seen the console, you know what an S3 bucket is, and services aren’t abstract names.

**A second certification.** The second associate cert is always faster than the first. Maybe half the material overlaps, and more importantly you already know how AWS writes questions.

**Consistency over intensity.** An hour every evening beats eight hours every other Saturday. Spaced repetition is real, and cramming fights against it.

What slows people down

**Starting with the wrong exam.** Picking a certification that doesn’t match your background costs weeks. Read [which AWS certification to take first](/blog/which-aws-certification-first/) before you commit.

**Watching instead of doing.** Video courses feel productive. Ten hours of video with no hands-on work will not get you through an associate exam. You need to build things.

**No deadline.** Open-ended study stretches forever. Pick a target month, even before you book.

**Restarting.** People who study for three weeks, take a month off, then come back have to redo a lot. Momentum is worth more than any individual study technique.

A schedule that works

Here’s the shape I’d suggest for an associate cert over eight weeks.

**Weeks 1–2: the map.** Read the official exam guide. Watch or read through the full service list once without trying to memorize anything. Take a diagnostic practice test and score badly on purpose, so you know where you stand.

**Weeks 3–5: the depth.** Work through domains in order of weight. Build as you go. Every time you meet a service, open the console and use it. Keep a running list of things you got wrong.

**Weeks 6–7: the pressure.** Full-length timed practice exams. Review every question, including the ones you got right by guessing. Rework your weak domains specifically.

**Week 8: the polish.** Light review, one final practice exam, then stop. Rest the day before.

If you’re on a tighter schedule, [a focused 30-day AWS study plan](/blog/30-day-aws-study-plan/) compresses this without cutting the parts that matter.

When to book the exam

Book when your full-length practice scores clear the pass mark consistently, with margin. Not when the calendar says eight weeks are up.

Some people book early as a forcing function. It works for a certain kind of person and costs everyone else $150. If you know you procrastinate without a deadline, book it. If you know you’ll panic, don’t.

The realistic total

For most people starting with some tech background and targeting Solutions Architect Associate: **about two months**, roughly 60 to 80 hours.

Starting completely fresh and doing Cloud Practitioner first, then an associate: **three to four months** total.

That’s a genuinely reasonable investment for a credential that opens doors in a field with a six-figure median. Just don’t let anyone sell you a weekend.