This is doable. People move into cloud from teaching, nursing, retail management, the military, and the trades every year. I’ve watched it happen plenty of times.

It’s also harder than the marketing suggests, and the people who succeed tend to do the same handful of things. Here’s the honest version.

Start with the one real prerequisite

There aren’t any formal prerequisites. You can register for any AWS exam tomorrow. But there’s one piece of background knowledge that determines how hard this will be, and it’s not AWS.

**It’s networking.**

If IP addresses, subnets, routing, and firewalls mean nothing to you, that’s the gap that will cost you the most time on an associate exam. Not the AWS part. The fundamentals underneath it.

Spend a week on general networking basics before you touch AWS material. Any free introduction will do. You need to understand what an IP address is, what a subnet does, what a firewall rule looks like, and roughly how traffic finds its way somewhere. That week will save you three later.

The path that works

Step 1: Cloud Practitioner (3–4 weeks)

Start here. Skip-the-Practitioner advice is aimed at people already working in tech, and it doesn’t apply to you.

This exam is partly designed for non-technical people who work around AWS. It builds vocabulary and gives you a map. Passing it also earns a 50% voucher toward your next exam, so it’s cheaper than the sticker price suggests.

More importantly, it gives you an early win. Career changing is a long project and evidence of progress matters.

Step 2: Build things (ongoing, starts now)

Not after. Now, alongside the studying.

Open a free tier account and work through real projects. [What to build on the free tier](/blog/aws-hands-on-practice-free-tier/) lists six in order, starting with a static website and working up to a VPC you design yourself.

This is the step people skip, and it’s the step that separates people who get hired from people who collect certificates. When an interviewer asks what you’ve done, “I passed an exam” is a weak answer. “I built a three-tier app in a VPC I designed, and here’s the decision I’d change” is a strong one.

Step 3: Solutions Architect Associate (8–12 weeks)

Give yourself more time than the standard estimate. Eight weeks is for people with infrastructure backgrounds. Ten to twelve is realistic for you, and that’s fine.

This is the certification that appears in job postings. It’s the one that matters for hiring.

Step 4: Apply while you study

Start at the halfway point of step 3, not after you pass. You’ll get rejections. You’ll also get interview practice while the material is fresh, and occasionally someone takes a chance on a candidate who’s visibly mid-journey and clearly serious.

The realistic timeline

**Four to six months** from standing start to associate certified, with projects behind you, studying evenings and weekends.

Then a job search on top of that, which for a career changer is often another three to six months. That’s not discouraging, that’s just the actual shape of it. Knowing the timeline upfront is what stops people quitting in month three.

What to expect that nobody warns you about

**You will feel lost in week two.** Everyone does. The service names are arbitrary, the acronyms pile up, and it feels like there’s no floor. This passes around week four when the categories start to stick.

**Video courses feel productive and aren’t enough.** Watching someone build something is not the same as building it. If you finish a week without opening the console, that week didn’t count.

**Your first role may pay less than the salary surveys.** The [numbers you’ll see quoted](/blog/aws-certification-salary/) are for people with experience. Your first cloud job is an entry point, and the pay catches up faster in this field than most.

**Nobody is going to ask about your old career in a bad way.** Career changers worry about this constantly. In practice, hiring managers care whether you can do the work. A teacher who can explain a VPC clearly is often a better hire than someone who can’t.

What actually gets you over the line

**Consistency.** An hour a night beats a marathon weekend, every time.

**Building.** I’ll keep saying it because it’s the thing people skip.

**A community.** Find people doing the same thing. Career changing alone is much harder than career changing with five other people in a group chat.

**Patience with the middle.** Month one is exciting, month four is a grind, month five is when it works. Most of the people who don’t make it quit in month four, not because they couldn’t do it, but because the exciting part ended and nobody told them that was normal.

It’s normal. Keep going.