AWS certifications come in four tiers, and the way they’re presented makes it look like a ladder you climb one rung at a time. You don’t have to, and for a lot of people you shouldn’t.

Here’s how the levels actually work and how to sequence them for where you’re starting.

The four levels

**Foundational** is the Cloud Practitioner. Broad, shallow, business-aware. It covers what the services are for and how AWS pricing and support work, without asking you to design anything.

**Associate** is where the real technical content starts. Solutions Architect Associate, Developer Associate, SysOps Administrator Associate, and Data Engineer Associate live here. These ask you to pick the right service for a scenario and justify the trade-off.

**Professional** is Solutions Architect Professional and DevOps Engineer Professional. Long, dense, multi-service scenarios where several answers work and you’re picking the best one under constraints. These are hard exams.

**Specialty** covers focused domains like security, networking, and machine learning. They go deep on one area and assume you already know the fundamentals.

There’s no enforced prerequisite between levels. You can register for a Professional exam tomorrow without holding anything else. Whether that’s wise is a different question.

The path that works for most people

If you’re new to cloud entirely

Start with **Cloud Practitioner**, then move to an **associate** cert.

The Practitioner isn’t strictly necessary, and plenty of people skip it. But if the vocabulary is unfamiliar, it gives you a map before anyone asks you to navigate. It’s also the cheapest exam at $100, and passing it earns you a 50% voucher toward the associate exam, which effectively makes it much cheaper than it looks.

If you already work in tech

Go straight to an **associate** cert. Skip the Practitioner.

If you’re a developer, sysadmin, or engineer who’s touched AWS at all, the Practitioner will mostly tell you things you know. Solutions Architect Associate is the usual choice because it’s the most widely recognized and the broadest. Developer Associate makes more sense if you’re writing application code against AWS services. Data Engineer Associate is the one to take if your work is pipelines and analytics.

If you’re already senior in AWS

Consider going straight to **Professional**. Passing it recertifies the associate below it anyway, so you’re not skipping anything permanently. Just be honest about your depth first. The Professional exams punish people who know services individually but haven’t designed complete systems.

Which associate cert to pick

This is the decision that matters most, and people get it wrong by picking whatever they saw mentioned most often.

• **Solutions Architect Associate** if you design or want to design systems, or if you’re not sure. It’s the default for a reason and the most commonly requested in job postings.
• **Developer Associate** if you write code that calls AWS services. Heavier on SDKs, deployment, and application-level patterns.
• **SysOps Administrator Associate** if you run and monitor infrastructure. The most operations-focused of the group.
• **Data Engineer Associate** if your world is ingestion, transformation, storage, and analytics.

We’ve got a full breakdown of [how to choose your first AWS certification](/blog/which-aws-certification-first/) if you want to think it through properly.

What it costs to walk the path

• Foundational: **$100**
• Associate: **$150**
• Professional and Specialty: **$300**

Plus applicable taxes depending on where you are.

The voucher matters here. Passing any exam earns a 50% discount toward your next one. Practitioner to associate becomes $100 then $75. Associate to professional becomes $150 then $150. Over a three-exam path, that’s real money.

How long the whole thing takes

Rough but realistic, assuming you have a job and study in the evenings:

• Cloud Practitioner: **two to three weeks**
• First associate cert: **one to two months**
• Second associate cert: **three to five weeks**, because the overlap is large
• Professional: **two to three months**, and don’t let anyone tell you it’s faster

The second associate is always quicker than the first. Roughly half of what you learned transfers, and you already know how AWS writes questions, which is worth more than people expect.

When to stop

You don’t need all of them. I’d push back on anyone collecting certifications for their own sake past the second or third.

A good stopping point for most careers is one associate cert that matches your job, plus hands-on work. Add a Professional when you’re doing that level of work or interviewing for it. Add a Specialty when a specific role asks for it.

Past that, you’re spending evenings on exams instead of building things, and the building is what actually makes you good.