From 0 to Golden Jacket: What I Learned Earning Every AWS Certification in 144 Days
This isn't a guide to collecting badges. It's a look at what worked, what didn't, and what I learned while completing all 12 AWS certifications in 144 days. From study habits and exam strategy to which certifications provide the most value for different roles, here's the map I wish I'd had on day one.
On December 26, 2025, I took the AWS Certified Cloud Practitioner exam.
At the time, I had no idea it would be the first of twelve certifications completed over the next 144 days.
That wasn't the original plan.
The goal was to get certified, strengthen my AWS knowledge, and better understand the value of the certification program. As someone who leads data engineering teams, I wanted firsthand experience before recommending certifications to others.
After the first few exams, I realized something interesting: the certifications were exposing gaps between what I knew and what I could confidently explain. There were plenty of AWS services I was aware of, had used occasionally, or had encountered in architecture discussions, but far fewer that I could discuss in depth. The certification process forced me to move beyond familiarity and develop a stronger understanding of how services fit together, where they excel, where they fall short, and the tradeoffs involved in choosing one solution over another.
At some point, I realized I was halfway through the catalog. Then most of the way through. Then close enough that not finishing felt wrong.
This article isn't a study guide, and it isn't an argument that everyone should earn twelve certifications in five months. Most people shouldn't.
Instead, it's a retrospective on what worked, what didn't, which certifications provided the most value, which were the most challenging, and which I'd recommend based on role, experience level, and career goals.
I Had to Figure Out How to Learn
For as long as I can remember, I've been a horrible test taker. I can build things. I can troubleshoot things. I can spend hours chasing down some weird production issue. Sitting down and taking a multiple-choice exam has never been my strong suit.
Pretty quickly, I realized a lot of the traditional advice didn't work for me. Marathon study sessions, endless videos, and trying to memorize AWS services weren't getting the job done.
My primary study resources were AWS Skill Builder and Tutorials Dojo. Skill Builder helped me understand AWS's perspective on topics, while Tutorials Dojo was invaluable for practice questions and identifying weak spots.
What worked was much more iterative.
Practice questions → find a gap → learn the concept → write it down → get quizzed on it → repeat.
The cheat sheets became a huge part of the process. If I couldn't explain something in a few bullet points, I probably didn't understand it very well.
I also used ChatGPT, Gemini, and Claude extensively. Sometimes to quiz me. Sometimes to validate concepts. Sometimes to challenge my reasoning. And occasionally for completely unnecessary pre-exam pep talks in the voice and tone of Luis Guzmán.
Was that necessary? Probably not.
Did it help? Somehow, yes.
The biggest lesson was that I had to stop worrying about studying the "right" way and start studying the way that actually worked for me.
What Worked (And What Didn't)
Schedule the Damn Exam
The single most effective thing I did was schedule the exam.
Not plan to take it. Not think about taking it. Schedule it.
Once the date was on the calendar, the decision had already been made.
What didn't work?
Waiting until I felt ready.
I don't think I felt ready for a single one of these exams.
Every time I thought, "Maybe I should push it out another week," the answer was usually the same: take the exam. Figure it out. Stop whining. Move on to the next one (hopefully).
Study Your Weaknesses
It's easy to spend time studying things you're already good at. It feels productive.
Spoiler alert: it is not productive at all.
The biggest gains came from finding weak spots and attacking them directly.
Networking was a repeat offender.
Practice Questions Are Feedback
I stopped treating practice exams like report cards.
A bad score wasn't a sign I was going to fail. It was a sign I found something I didn't understand yet.
Wrong answers gave me a roadmap.
Learn Tradeoffs, Not Services
As the exams get harder, memorization becomes less useful.
AWS isn't testing whether you've heard of a service. They're testing whether you understand why it's the best answer, what its limitations are, and what tradeoffs come with it.
That mindset shift made a huge difference.
AI Was My Study Buddy
I used ChatGPT, Gemini, and Claude constantly throughout this journey. Not to generate answers, but to challenge my understanding.
Some of the most useful things I used them for were:
- Generating cheat sheets
- Creating quizzes
- Building worksheets
- Explaining concepts differently
- Challenging architectural decisions
- Finding holes in my reasoning
A few prompts I used regularly:
Generate a Cheat Sheet
"Create a one-page AWS certification cheat sheet for [TOPIC]. Focus on key concepts, common exam traps, service comparisons, limitations, and decision criteria. Format it as concise bullet points optimized for exam review."
Generate a Quiz
"Act as an AWS certification instructor. Quiz me on [TOPIC] one question at a time. Do not reveal the answer immediately. After I answer, explain why the correct answer is right and why the other options are wrong."
Generate a Worksheet
"Create a worksheet for [TOPIC] with scenario-based questions that require selecting between AWS services. Focus on tradeoffs, security, reliability, operational excellence, and cost optimization. Include an answer key at the end."
Which Certifications Delivered the Most Value?
Solutions Architect Associate
If someone asks me where to start, this is almost always the answer.
It touches nearly every major AWS domain and builds a foundation that makes everything else easier.
Solutions Architect Professional
The exam everyone talks about.
This is where AWS stops asking about services and starts asking about tradeoffs. And yes, sometimes the questions and answers felt like : choose the best worst option.
Security Specialty
One of the most broadly useful certifications in the catalog.
Identity, encryption, governance, logging, monitoring, detective controls, preventative controls. These concepts show up everywhere.
DevOps Engineer Professional
The most operationally focused certification in the catalog.
If you're responsible for running systems in production, there's a lot to gain here.
Advanced Networking Specialty
I hated it.
I also learned a tremendous amount from it.
Both things can be true.
The Hardest Exams
Everyone asks.
My answer:
- Advanced Networking Specialty
- Solutions Architect Professional
- DevOps Engineer Professional
- Security Specialty
Advanced Networking was the only exam I failed.
BGP. Direct Connect. VPNs. Route propagation. Hybrid networking.
There is nowhere to hide if networking isn't one of your strengths.
This was the only certification that forced me to completely regroup, adjust my approach, and come back for a second attempt.
Question 17 isnt going to stop me.
What Would I Recommend?
Not everyone needs twelve certifications.
Most people shouldn't try to earn twelve certifications.
New to AWS
Cloud Practitioner → Solutions Architect Associate
Architects
Solutions Architect Associate → Solutions Architect Professional
Data Engineers
Data Engineer Associate → Solutions Architect Associate → Machine Learning Engineer Associate
DevOps Engineers
Developer Associate → Cloud Operations Engineer Associate → DevOps Engineer Professional
Security Engineers
Solutions Architect Associate → Security Specialty
AI / ML Practitioners
AI Practitioner → Machine Learning Engineer Associate
Technical Leaders
Cloud Practitioner and Solutions Architect Associate provide the most value per hour invested.
Final Thoughts
Looking back, the most valuable part of this journey wasn't collecting twelve certifications.
It was discovering where my knowledge was shallow, where my assumptions were wrong, and where I needed to improve.
The certifications didn't teach me AWS from scratch. They forced me to organize what I knew, expose what I didn't, and get much better at understanding and explaining tradeoffs.
Also, networking is still ridiculous.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article