Thirty days is tight for an associate exam but it’s doable if you’ve got some technical background and you can give it 12 to 15 hours a week. If you’re starting completely from zero, be honest with yourself and give it eight weeks instead. [Realistic timelines are here](/blog/how-long-does-it-take-to-get-aws-certified/).

Here’s the plan I’d give you.

Before day one

**Download the official exam guide** for your certification. Not a summary. The actual PDF from AWS. It lists the domains, their weightings, and the in-scope services. This is your syllabus and everything below is organized around it.

**Create a free tier account** if you don’t have one.

**Take a diagnostic practice exam cold.** You’ll score badly. That’s the point. You need a baseline and a map of your weak domains before you spend a single hour studying.

Week 1: build the model

Goal: understand the shape of AWS, not memorize it.

• Work through the major service categories: compute, storage, networking, databases, security, monitoring.
• For each service, answer four questions: what problem does it solve, what goes in, what comes out, and what’s the closest alternative?
• **Build one thing.** Launch an EC2 instance in a VPC you made yourself. Put it in a public subnet, reach it, then move it to a private one and figure out why you can’t.
• Don’t touch practice questions yet beyond your diagnostic.

End of week 1, you should be able to explain the difference between S3, EBS, and EFS to somebody without looking it up.

Week 2: depth on the heavy domains

Goal: cover the domains that carry the most weight.

• Check the domain percentages in your exam guide and work them in order of weight. If a domain is 30% of the exam, it gets 30% of your week.
• Go deeper on the service comparisons that decide questions. For Solutions Architect, that’s things like [the comparisons that decide SAA-C03 questions](/blog/aws-service-comparisons-saa-c03/).
• **Start doing practice questions in small sets**, 20 at a time, untimed. Review every single one, including correct answers.
• Keep a running “wrong answer log” with one line per miss: what the question tested and why you missed it.

Week 3: pressure and patterns

Goal: learn how AWS writes questions.

• **Switch to timed sets.** Two minutes per question. This is the week you learn pacing.
• Read your wrong answer log and look for patterns. Most people find their misses cluster into two or three specific causes, not twenty different knowledge gaps.
• If you’re misreading scenarios rather than lacking knowledge, spend an evening on [how to actually read an AWS exam question](/blog/how-to-read-an-aws-exam-question/). It’s the highest-leverage fix available.
• **Take one full-length timed exam** at the end of the week, at the same time of day you’ll sit the real one.

Week 4: close the gaps and stop

Goal: fix what’s broken and arrive rested.

• **Days 22–25:** target your weakest domains specifically. Build the things you’re shaky on rather than rereading about them.
• **Days 26–28:** two more full-length timed exams. You want to be clearing the pass mark with margin, consistently, not once.
• **Day 29:** light review of your wrong answer log only. No new material.
• **Day 30:** rest. Genuinely. Cramming the night before costs you sleep, and sleep is worth more over a two-hour exam than anything you’d learn.

What to cut if you fall behind

You will fall behind at some point. Here’s the priority order when you have to triage.

**Keep:** the exam guide domains by weight, hands-on building, full-length timed practice, and your wrong answer log.

**Cut first:** video courses you’re half-watching. Services that appear in no domain on your exam guide. Deep dives into things you already know. Note-taking that’s really just copying.

**Never cut:** the full-length timed exams. If you’ve only got time for one thing in the last week, it’s these.

The rules that make it work

**Same time every day.** Decision fatigue kills study plans. Pick a slot and defend it.

**Build, don’t just read.** If you finish a week without opening the console, the week didn’t count.

**Review correct answers too.** If you got it right by eliminating two options and guessing, that’s a gap wearing a disguise.

**Don’t book the exam on day one.** Book it around day 20, once you can see where your practice scores are heading.

Thirty days is enough if you spend it on the right things. Most people who fail a one-month attempt didn’t run out of time. They spent three of the four weeks watching videos.