AWS Builder Center
Predicting the Voids: A Possible Blueprint for AWS Certifications

Predicting the Voids: A Possible Blueprint for AWS Certifications

I share how I reimagined the AWS certification map. I proposed two strategic shifts that transform the scattered exams into three highly focused, symmetrical career paths: Architecture, DevOps, and Data & AI.

Disclaimer up front: I do not have any unpublished, insider knowledge from AWS. Although I am an AWS Champion Instructor, an AWS Community Builder, and hold every active AWS certification (plus a few others), the thoughts below are drawn entirely from my own experience as a student, a certified professional, and a teacher.

Let me tell you a story.

A long, long time ago in a galaxy far, far away (okay, fine, it was Petah Tikva. Close enough; if you know, you know), I was a high school history teacher. I ran a special class for underachieving kids. In this program, we tried one last push to get them full high school diplomas. That meant they had to pass all government final exams.
When the results came in, my class scored so well that we were actually flagged for possible cheating. The smoking gun? The final prep test I had created for them to practice on was uncannily close to the real questions on the government exam.
But I didn’t cheat. I just listened.
Leading up to the exam, I sat in every meeting with the history superintendent. I noted every remark, every curriculum update, and every example she gave. But most importantly, I listened to what she didn’t say. I mapped out the negative space. She talked over every historical era, yet she withheld an example question; I deduced she did so purposefully. Those were the topics she was keeping in her pocket for the actual test. I created my practice test from those voids. And that is exactly how my “underachieving” class achieved a 100% pass rate with an average of 80/100.
Now, let’s apply that same “void-reading” logic to the current state of AWS Certifications.

The True Purpose of a Certification

Before we start rearranging the furniture, we have to ask: what is an IT certification actually supposed to serve?
It’s not just a shiny digital badge for your LinkedIn profile (though that doesn’t hurt). A well-designed certification program serves two vital purposes:
  1. For the Employer (Baseline of Trust): It creates a standardized benchmark. It proves to a hiring manager that you don’t just know how to click around the AWS Management Console, but that you understand the underlying architecture, security guardrails, and industry best practices. It removes the guesswork from hiring.
  1. For the Learner (Structured Roadmap): The cloud is an infinite, overwhelming ocean of services. Without a roadmap, it’s easy to drown in the documentation. Certifications provide a structured curriculum. They give you clear, escalating milestones to aim for so you know exactly what to learn and when to learn it.
But why so many? Why not just one giant “AWS Certified” badge?
You might be asking, if the goal is a standardized benchmark, why do we need 12 different exams across varying levels and subsets? Why not just create one massive exam to have it all in one?
Because one single exam would either be impossible to pass or completely useless. If it covered every AWS service in depth, it would take a week to read and a lifetime to study. If it covered everything superficially, it would be a mile wide and an inch deep, proving nothing.
The cloud is too vast, and the real-world tech industry relies on a strict division of labor. A software developer writing Lambda functions does not need to understand the complex BGP routing of AWS Direct Connect as a Network Architect does. A Machine Learning expert doesn’t need to configure organization-wide Security Control Policies (SCPs) like a SecOps administrator.
We need specific subsets to mirror actual job roles. We need varying levels, from fundamental to Professional, to distinguish between someone who can execute a blueprint and someone who can design the blueprint.
When a certification path is messy or contains orphaned exams, it fails this very purpose. It creates confusion instead of mirroring the real-world flow of a career.

The Psychology of a Coherent Track

When a certification ecosystem gets too messy, it triggers a psychological phenomenon known as analysis paralysis.
When a student or professional is presented with too many disconnected options — especially when none of them have a clear, definitive advantage — they get stuck. They spend so much energy trying to figure out what to study next that they end up choosing nothing at all. This is why a coherent, logically flowing track is so important. Knowledge is a stack. A coherent track does three critical things for a professional:
  • It Builds Momentum: When you pass an Associate exam and look toward the Professional tier, it shouldn’t feel like jumping across a canyon. It should feel like climbing the next rung on a ladder. A coherent track allows you to leverage the concepts you just mastered and stack new, complex ideas directly on top of them.
  • It prevents “Certification Fatigue”: Studying for these exams is exhausting. If an exam is orphaned from the rest of the ecosystem, taking it feels like a side quest that pulls you away from your main career goals. A cohesive track ensures every hour of study pushes you further up your specific mountain.
  • It tells a Unified Story: To a recruiter, a resume with a random smatter of badges looks unfocused. But a resume that shows a direct, escalating progression — say, from Associate Developer to Associate CloudOps to Professional DevOps Engineer — tells a compelling story. It says, “I have a plan, I have a specialty, and I execute it.”

The Problem: It’s “Almost” Perfect

Currently, AWS has 12 certifications spread across 4 levels: Foundational, Associate, Professional, and Specialty.
If you look closely at AWS’s recertification policies online, you can see they are already operating on a nested, hierarchical structure. Currently, passing a Professional-level exam automatically recertifies you for its corresponding Associate-level exams underneath it.
For example, taking the AWS Certified DevOps Engineer — Professional exam automatically renews the two Associate exams that naturally feed into it: Developer and CloudOps. The exact same 2-for-1 logic applies beautifully to the Data and Machine Learning side of the house.
The DNA for a perfect, symmetrical certification tree is already there. But the structure is almost perfect. It’s almost pretty. And AWS doesn’t do “almost.”
The glaring problem is that the AWS Certified Solutions Architect — Professional exam is stuck. It currently sits at the top of its pillar with only one Associate exam (Solutions Architect — Associate) underneath it. Meanwhile, we have two Specialty certifications (Security and Advanced Networking) floating in the void, orphaned from the rest of the flow and not directly correlating with any Professional tier.
It feels unbalanced. But by reading the voids — looking at what AWS has already done with the other tracks — we can see exactly how it should be fixed.

The Solution: Creating 3 Perfect Tracks

To achieve a perfectly balanced certification matrix and fix the lopsided Solutions Architect tier, AWS needs to formalize these exams into three distinct “Tracks.” To do this, we only need to make two strategic adjustments to the existing Specialty exams:
  • Downgrade Security Specialty to an Associate: Let’s be brutally honest. As it stands today, the Security Specialty is, in my opinion, already on par with the difficulty of an Associate-level exam. Furthermore, in the modern cloud, security is not a niche “specialty” — it is a foundational requirement. It should be rebranded as the AWS Certified SecOps Engineer — Associate and nested directly under the Solutions Architect track.
  • Retire and Integrate Advanced Networking: The Advanced Networking Specialty was the hardest exam I ever took by a massive gap, yet it is arguably the least broadly useful as a standalone badge. How do we fix this? AWS should dissolve this specific exam and integrate those heavy, complex networking questions directly into the Solutions Architect — Professional exam. A true Pro Architect should inherently understand Advanced Networking anyway; it shouldn’t be a separate silo.

The New Architecture: Perfect Symmetry

If AWS makes those two practical adjustments, all the puzzle pieces suddenly snap into place. We are left with a beautifully structured, perfectly symmetrical certification tree.
We get 3 distinct Tracks. Each track contains exactly 1 Professional certification, which is supported perfectly by 2 Associate exams.
Here is what that possible, elegant structure looks like:

Track 1: The Architecture Track

This track becomes the ultimate path for infrastructure design, balancing general architecture with strict security practices.
Professional: AWS Certified Solutions Architect — Professional (Now bolted with the weight of Advanced Networking)
  • Nested Associate 1: AWS Certified Solutions Architect — Associate
  • Nested Associate 2: AWS Certified SecOps — Associate (Formerly Security Specialty)

Track 2: The Development & Operations Track (Already Exists)

This is the builder-and-maintainer track. It perfectly marries code creation with operational excellence to create a true DevOps master.
Professional: AWS Certified DevOps Engineer — Professional
  • Nested Associate 1: AWS Certified Developer — Associate
  • Nested Associate 2: AWS Certified CloudOps Engineer — Associate 

Track 3: The Data & AI Track (Already Exists)

This track reflects the modern reality of the cloud. You cannot do cutting-edge AI without rock-solid data engineering underneath it.
Professional: AWS Certified Generative AI Developer — Professional
  • Nested Associate 1: AWS Certified Data Engineer — Associate
  • Nested Associate 2: AWS Certified Machine Learning Engineer — Associate
(And of course, sitting beneath all three of these tracks is the sturdy root system: the AWS Certified Cloud Practitioner and AWS AI Practitioner, feeding candidates upward into their chosen path).

The Takeaway

Just like my students, AWS candidates need a curriculum that makes sense. They need a path that builds upon itself logically, rather than throwing them curveballs.
By looking at what is missing- the lopsided gaps in the current certification paths- we can see the possible end-state of the AWS training journey. By organizing these 12 certifications into three distinct, perfectly balanced tracks, candidates would have a crystal-clear roadmap from Foundational knowledge all the way up to professional mastery.
There would be no orphaned exams. No confusing overlaps. Just a clean, escalating path of cloud expertise that cures analysis paralysis and rewards candidates for continuing their journey.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article