Here’s the part that surprises people: **there are no prerequisites for any AWS certification.**

None. You can register for the Solutions Architect Professional tomorrow with zero cloud experience and no other certifications. AWS won’t stop you. There’s no gatekeeping, no proof of employment, no required training course.

What AWS publishes is **recommended experience**, which is guidance, not a rule. And the gap between “required” and “recommended” is where most of the confusion lives.

What AWS recommends

Broadly, AWS suggests something like:

• **Cloud Practitioner**: around six months of general AWS exposure, in any role including non-technical ones
• **Associate level**: about a year of hands-on experience with AWS
• **Professional level**: two or more years designing and operating AWS solutions
• **Specialty**: significant depth in that specific domain

Treat these as descriptions of who the exam was written for, not as a bar you must clear. They tell you the assumed starting point, which is genuinely useful for judging how much ground you’ll need to cover.

Can you pass with no experience?

**Cloud Practitioner: yes, comfortably.** This exam was designed partly for people in sales, finance, and project roles who work around AWS without building on it. A few weeks of study from a standing start is normal.

**Associate level: yes, but you’ll have to build things.** This is the honest answer. You can absolutely pass Solutions Architect Associate without a cloud job, and plenty of people do. What you can’t do is pass it purely by reading. The questions are scenario-based, and scenarios only click once you’ve seen the console, made a VPC, attached a security group, and watched something fail because you got a route table wrong.

The free tier exists for exactly this. Use it.

**Professional level: technically yes, practically no.** I wouldn’t recommend it. These exams assume you’ve made architectural decisions under real constraints, with a budget and a deadline and someone to answer to. That’s very hard to simulate. People do pass without the background, but they study for a long time and it’s not the efficient path.

The thing that substitutes for experience

Building.

Not watching someone build in a video. Doing it yourself, badly, and fixing it. A weekend spent standing up a VPC with public and private subnets, putting an EC2 instance in each, and getting the private one to reach the internet through a NAT gateway will teach you more about networking questions than ten hours of lectures.

When you hit an exam question about a private subnet, you won’t be recalling a definition. You’ll be remembering the afternoon you spent figuring out why your instance couldn’t download updates. That memory is what you’re actually studying for.

What you do need

Forget experience for a moment. Here’s what genuinely determines whether you’ll pass:

• **Comfort with technical reading.** These exams are dense. If long technical prose is a struggle, that’s a bigger obstacle than missing AWS background.
• **Basic networking literacy.** IP addressing, subnets, routing, firewalls. You don’t need to be a network engineer, but if none of those words mean anything yet, start there. It’s the most common gap.
• **A free tier account.** Non-negotiable for associate level.
• **Patience with the question style.** AWS writes long scenarios with deliberate distractors. This is a learnable skill, separate from knowing AWS.

If you’re career changing

This is the most common version of the question, so let me answer it directly.

You can do this. People move into cloud from teaching, from the military, from retail management, from help desk work, every single year. The path that works looks like:

1. **Cloud Practitioner** to build vocabulary and confidence. Three weeks or so.

2. **Build things** on the free tier while you study. Not optional.

3. **An associate cert**, usually Solutions Architect. One to two months.

4. **Apply aggressively** while you study, not after.

What you can’t do is treat certification as a replacement for the building part. A certified candidate who’s never opened the console gets found out in the first technical interview, and it’s an unpleasant experience for everyone.

Don’t wait until you feel ready

The most common mistake isn’t starting too early. It’s waiting.

People spend a year telling themselves they need more experience before they’re allowed to attempt an associate exam. Meanwhile the exam is sitting right there with no prerequisites, and studying for it *is* how you get the experience.

Start. Build as you go. Book the exam when your practice scores say you’re ready, not when you feel worthy of it.