AWS certification career paths: which certification for which role
Updated
The right AWS certification depends on the role you are aiming for: Cloud Practitioner for cloud fluency in any job that touches AWS, Solutions Architect – Associate for designing and building (and for general cloud-engineering roles — it is the broadest), Developer – Associate for application development, and the CloudOps associate for operations, SRE, and systems administration. Professional and specialty certifications come later, once you have real experience to build on. No AWS exam has prerequisites, so the levels are a recommended progression rather than a locked ladder — but choosing by target role, not by prestige, is what makes the studying double as job preparation. Here is the honest map.
How the AWS certification levels work
AWS organises its certifications into four tiers, and understanding them stops you over- or under-shooting:
- Foundational — Cloud Practitioner. Concepts, core services, pricing, security basics. No technical background assumed.
- Associate — Solutions Architect, Developer, and CloudOps. The recognised professional entry tier; AWS recommends around a year of hands-on experience for each.
- Professional — Solutions Architect and DevOps Engineer. Deep, scenario-heavy exams that assume years of real experience.
- Specialty — narrow, deep exams (security, networking, machine learning and others) for people already working in that niche.
Cloud Practitioner: fluency, and the on-ramp
The Cloud Practitioner is not a certification for cloud engineers — it is a certification for everyone around them, and an on-ramp for people becoming them. If you work adjacent to the cloud — sales, product, project management, finance, support, leadership — it gives you genuine fluency: what the core services do, how the pricing model works, what the security responsibilities are. That fluency is the difference between sitting in cloud conversations and contributing to them.
For aspiring engineers, it is the honest first step when you are new to the cloud: it builds the vocabulary and the mental model the associate exams assume, without the technical depth. It will not, by itself, qualify you for an engineering role — treat it as the foundation it is named for, not the destination.
Solutions Architect – Associate: the broadest credential
If you want one certification for cloud-engineering work generally, this is it. The Solutions Architect – Associate covers designing systems on AWS — compute, storage, networking, databases, security, cost — which is why it maps to the widest set of roles: cloud engineer, solutions architect, infrastructure engineer, platform engineer, and plenty of jobs that are none of those by title but all of them in practice. It is also the associate that appears most often in job descriptions, which makes it the strongest single signal on a CV.
Its breadth is the point and the caveat. It teaches you how AWS fits together rather than making you deep in any one discipline, so pair it with hands-on building — and if your target role is specifically development or operations, one of the other two associates may serve you better as a first or second step.
Developer and CloudOps: the specialist associates
The Developer – Associate is for people who build applications on AWS. It goes deeper on the developer-facing services — serverless, APIs, queues, containers, deployment tooling — and on how code actually interacts with the platform: SDKs, permissions, debugging, release practices. If your day job (or target job) is writing software that runs on AWS, it matches the work more closely than the architecture exam does.
The CloudOps associate is the operations counterpart: running workloads once they exist. Monitoring, alerting, automation, reliability, networking in practice, cost and compliance housekeeping — the daily reality of cloud operations, SRE, and systems administration roles. If you come from a sysadmin or IT-operations background, it is often the most natural associate, because it certifies the cloud version of work you already understand.
Professional and specialty: specialisation, later
The professional and specialty tiers are where certifications stop being entry signals and start being depth signals. The Solutions Architect – Professional and DevOps Engineer – Professional exams are long, scenario-driven, and genuinely difficult without years of hands-on work behind you; the specialty exams assume you already operate in their niche. Attempting them early usually buys a retake fee and teaches you less than the same hours spent building.
The honest sequencing: associate first, then real experience, then a professional or specialty exam when your work is already pushing you into that depth. At that point the exam formalises what you have been doing — which is when the harder certifications are at their most valuable and their most passable.
How the paths stack in practice
Certification paths are cumulative, not parallel tracks you must choose between forever. The associates share a large common core — the same services, security model, and networking underneath different emphases — so a second associate is meaningfully cheaper to earn than the first, and a developer who adds the CloudOps exam (or vice versa) is describing a very employable shape: someone who can build things and run them.
A realistic default path: Cloud Practitioner if you are new (skip it if you are already technical and hands-on), then the associate matching your target role, then depth — more building, a second associate if a role calls for it, and a professional exam once experience justifies it. Choose each step by the job you want next, and let the role, not the badge count, drive the sequence. Whether any given step is worth it for you is its own question — we have written honestly about that elsewhere on the blog.