In 2025, I earned two AWS certifications:
- AWS Cloud Practitioner (Intro to Cloud 101)
- AWS Generative AI Foundations
Total cost: $0 (used free training + AWS Skill Builder) Total time: ~40 hours of study Total coffee consumed: Approximately one small coffee plantation's worth ☕ Total job offers directly from the certs: Exactly 0.
So was it worth it?
...Actually, yes. But not for the reasons you'd expect.
The Certification Debate
Let me address the elephant in the room:
"Certifications are worthless. Just build projects."
This take is half right and half "I don't understand how corporate hiring works."
Certifications alone won't get you hired. Nobody looks at a resume and says "Oh, they have AWS Certified! Cancel the other interviews! Roll out the red carpet!" 🍾
But certifications do three things that projects can't:
1. Force Structured Learning
I can "learn AWS" by watching YouTube for 3 hours. But will I remember the difference between S3 storage classes? Will I understand IAM policies deeply? Will I know why us-east-1 is both a blessing and a curse?
Probably not. I'll probably just make everything public-read and hope for the best.
Please don't do this. Please. I'm begging. 🙏
The certification exam forced me to actually understand concepts I would have glossed over otherwise.
Did you know? There are 7 S3 storage classes. I know this now. I retain this information against my will. The exam made sure of it.
2. Provide Credibility for Non-Provable Skills
How do you prove you know cloud architecture on a resume?
-
Projects: "I deployed this to EC2." (Okay, but anyone can spin up an instance. My grandmother could spin up an instance. My grandmother has. Don't ask.)
-
Certification: "I passed a proctored exam testing 65 topics while a stranger watched me through my webcam to ensure I didn't look at a sticky note." (Significantly harder to fake.)
For skills that don't have visible outputs, certs fill the gap.
3. Gate Access to Some Opportunities
Certain enterprise clients and government contracts require certified engineers. Not having the cert literally disqualifies you.
Is it gatekeeping? Yes. Is it reality? Also yes. Do I like it? No. Did I do it anyway? Obviously. Would I do it again? checks notes ...Yes.
Did You Know?
Trivia: AWS has 12 certification paths, from entry-level (Cloud Practitioner) to specialty (Machine Learning, Security, Networking). The average salary bump from one AWS certification is $12,000-$15,000 annually in the US. In the Philippines, it's less dramatic but still enough to buy a lot of extra rice. 🍚
My Study Strategy (The Free Version)
I didn't pay for expensive bootcamps. Here's what worked:
1. AWS Skill Builder (Free Tier)
AWS has official training content. It's dry. Like, "eating saltine crackers in the desert while reading a insurance policy" dry. But it's accurate.
I used it for foundational concepts and to ensure I wasn't just learning from random internet people who might be wrong.
2. Tutorials Dojo Practice Exams
The real MVP. These practice tests mirror the actual exam format.
I failed my first practice exam with 55%. I felt personally attacked by a multiple choice question.
By the fifth attempt, I was hitting 85%.
Pro tip: If you can pass Tutorials Dojo exams, you can pass the real thing. If you can't, rescheduling is cheaper than failing. And less embarrassing.
3. Hands-On Labs
I spun up actual AWS resources:
- EC2 instances (free tier, calm down)
- S3 buckets for static hosting
- Lambda functions for serverless experiments
- One load balancer I forgot to turn off (expensive lesson, 0/10 recommend)
Reading about cloud is not the same as clicking through the console and wondering why your bill is $0.12.
Did you know? AWS gives you a cost alarm feature that will email you before you accidentally spend $500 learning about auto-scaling. Use it. Trust me. USE IT.
4. Two Weeks of Focused Panic
I didn't study for months. I blocked 2 hours daily for 2 weeks before each exam.
Intensity > duration.
Also, panic is an incredible motivator. The fear of wasting exam time is real.
The Generative AI Certification
This one was special.
AWS released the Generative AI certification in 2024, and I took it in 2025. It covers:
- Foundation models and their architectures
- RAG (Retrieval Augmented Generation)
- Bedrock (AWS's managed AI service)
- Prompt engineering basics
- How to talk about AI without embarrassing yourself in meetings
As someone who works with AI daily, 60% was review. But the other 40% filled gaps I didn't know I had—especially around enterprise AI governance.
Basically: It taught me how to put "AI Safety" on a slide deck without laughing.
Now I can say "we need guardrails around our generative AI implementation" with a straight face. Career milestone unlocked.
What I'd Tell Past Me
1. Start with Cloud Practitioner
Even if you're experienced, it builds a shared vocabulary. Architects use specific terms (VPC, NACL, SG), and you need to speak the language.
It's like learning grammar before writing poetry. Boring but necessary.
2. Don't Over-Study
You don't need to memorize every service. There are like 200 of them. Nobody knows all 200. AWS employees don't know all 200.
Focus on:
- Core compute (EC2, Lambda, ECS)
- Storage (S3, EBS, EFS)
- Networking (VPC, subnets, gateways) — The scary part
- Security (IAM, policies, roles) — The boring part that's actually critical
The rest you can learn on the job (or Google while pretending to look thoughtful in meetings).
3. Pair With Real Projects
I deployed my portfolio to AWS (EC2 + Load Balancer) the same week I was studying. Every concept became concrete.
Also expensive, because I forgot to turn off the Load Balancer.
Learn from my mistakes. Delete. Your. Resources.
The Bottom Line
Are AWS certifications "worth it" in 2025?
If you:
- Already have a strong portfolio → Certs are nice-to-have
- Work in enterprise/consulting → Certs are often required
- Want structured cloud education → Certs are excellent guides
- Think a cert will replace skills → You're going to be disappointed
- Want to flex on LinkedIn → I mean... you could? But don't be that person.
I don't regret the 40 hours. They accelerated my understanding of cloud in ways random YouTube tutorials wouldn't have.
But I also didn't put "AWS CERTIFIED 🏆🎉🚀" in my LinkedIn headline.
Because at the end of the day, it's just a badge.
What matters is what you build with the knowledge behind it.
(And remembering to delete your unused EC2 instances. Please remember to delete them. I will keep repeating this. The billing alerts are not a joke.) 💸
