How long to study for AWS Cloud Practitioner? Plan in hours, not weeks
On this page
Short answer
20 to 40 hours, which is two to six weeks for most people at a realistic evening pace.
Plan in hours rather than weeks: weeks are what you have, hours are what you spend. And put the second half of those hours into answering questions you have not seen, not into re-reading notes that already feel comfortable.
Why the "two weeks" and "two months" answers are both true
They describe different people. Your starting point moves this more than any study method does.
| Where you are starting from | Realistic hours | Why |
|---|---|---|
| Already work with AWS | 10–15 | You are learning exam vocabulary, not concepts |
| Work in IT, little cloud | 20–25 | Concepts transfer; the service catalog is the work |
| Technical role, no infrastructure | 25–35 | Shared responsibility and billing models are genuinely new |
| No IT background at all | 35–50 | You are learning what a server is and what AWS calls theirs |
If you are in the last row, the number is not a discouragement. The exam is passable from there — it is designed to be. It just takes the hours it takes, and a plan built on somebody else's two weeks will feel like failure when it is nothing of the sort.
How to split the hours
The split matters more than the total. A rough shape that works:
- First 20% — read the exam guide. It is published, it is free, and it lists the four domains with their weights. Most people find it in week four and wish they had found it in week one. It is the syllabus; everything else is commentary on it.
- Next 40% — cover the ground. Free AWS Skill Builder training or a video course, whichever suits how you learn. Do this once, at pace. Do not try to memorize as you go.
- Next 30% — answer questions you have not seen. This is the part people skip and the part that decides the outcome. Every wrong answer is a specific, actionable gap; every set of twenty produces a short list of things to fix that evening.
- Final 10% — a full timed run, and the gaps it exposes. When to take a full practice exam and how to read the result is worth its own read; the summary is twice, and not in week one.
The split that quietly fails
Eighty per cent watching videos, twenty per cent on questions, feeling productive throughout. It fails because video is a recognition activity: everything the instructor says sounds right, because it is right and they just said it.
The exam does not ask you to recognize a correct statement. It asks you to choose between four statements that all look plausible. That is a different skill and it is only built one way.
Twenty minutes that are worth three hours
Open a free-tier AWS account and launch something. Anything. An S3 bucket, a tiny EC2 instance, a Lambda function that returns a string. Then look at the billing console, then delete it.
The service names stop being a vocabulary list the moment you have touched three of them. Cloud Technology and Services is 34% of the exam — the largest domain — and it is almost entirely "which service does what". Twenty minutes in the console does more for that domain than an hour of any other activity.
Set a billing alert first.
The signal that you are ready
Not a score. Not a percentage. Not a number of weeks.
Unseen questions stop surprising you. That is the whole signal. When you can work through twenty questions you have never met and finish without a single "where did that come from", you are ready — regardless of what any practice exam reported.
Two corollaries people find uncomfortable:
- A practice score near the pass mark is the most dangerous result to receive. Practice exams are not calibrated against the real one and cannot be. Near-the-line scores invite a booking that a second $100 then pays for.
- Keep a reserve of unseen questions for the final week. If you have burned through every bank you own by the halfway point, you no longer own a way to measure readiness. That is a worse position than being behind schedule.
A schedule that fits around a job
Thirty hours at five hours a week is six weeks. At ten hours a week it is three. Both work; what does not work is thirty hours crammed into the last four days, because the failure mode of this exam is confusing familiarity with knowledge, and cramming manufactures familiarity efficiently.
A workable pattern for six weeks:
- Weeks 1–2: exam guide, then cover the ground. Do not test yourself yet, you will only discourage yourself.
- Week 3: the console session, and start topic sets — twenty questions on one domain at a time.
- Week 4: first full timed exam. Read the domain breakdown, not the score.
- Week 5: work the gaps that exam found, using topic sets.
- Week 6: second full exam on unseen questions. Book the real one when it stops surprising you.
Book the exam after week four, not before you start. Booking early as motivation is a well-meant trick that works right up until the week where life happens.
What we are building
We are writing a free Cloud Practitioner question bank: every wrong option carries its own explanation, every question cites the AWS documentation behind it, and the spread follows the published domain weights rather than whatever was easiest to write.
Where it stands, plainly: it is written and open to practice with, free — but every question in it is still a draft that has not been reviewed yet. Review means a person reads each question and checks it against the AWS documentation it cites — today, our founder — and that step is still ahead. The form below is how to hear about it, and we send nothing else.
The one-line version
Twenty to forty hours, weighted so the second half is questions you have not seen. Read the exam guide first, spend twenty minutes in the console, and book when unseen questions stop surprising you rather than when the calendar says six weeks are up.
Practice AWS Cloud Practitioner free
A short placement test puts an estimated score on the real exam scale, then practice goes after the topics you miss. No account needed to start.
Start practicing freeNot ready to start yet?
Leave an email and we will send the occasional AWS Cloud Practitioner study guide. Nothing else.
Keep reading
- Is AWS Cloud Practitioner worth it? An honest answer, by situationWorth it for some people and a waste of $100 for others — and the difference is not how badly you want a cloud job. Four situations, answered separately.
- Cloud Practitioner vs Solutions Architect Associate: which one to sitCloud Practitioner is not a prerequisite for Solutions Architect Associate, and for people already in IT it is often a detour. How the two exams differ, and the self-test that answers it.
- AWS Cloud Practitioner exam cost: $100, and what surrounds itThe CLF-C02 exam is $100, but that is not what it costs you. Retake rules, regional pricing, the free training that actually exists, and the one expense nobody budgets for.