After six months of studying, the day had finally arrived.
On a Tuesday morning at 7:45 AM, I started the check-in process for my AWS Certified Solutions Architect – Associate exam. I took the required photos, completed the identity verification, and spoke with the proctor before beginning the exam.
For the next two and a half hours, I worked through each question one by one. Some answers came quickly, while others I flagged to revisit later. As the timer counted down, I focused on staying calm and making the best decision I could for each question.
Then the five-minute warning appeared.
"Okay, time to wrap this up."
I reviewed the questions I had flagged, made my final decisions, and clicked Submit.
With the exam complete, I closed my laptop, took a deep breath, and went back to work, knowing I'd done my best.
A little while later, I glanced at my Outlook inbox and noticed an email with the subject:
"Congratulations! You've received..."
I paused for a second, wondering what it was about.
I opened the email, and there it was:
"Congratulations! You've earned the AWS Certified Solutions Architect – Associate badge."
For a moment, I just smiled.
My first thought was:
"Oh... really? 😆 I couldn't believe what I was seeing, but that was such great news!"
It was an incredibly rewarding feeling. All the studying, practice exams, and hours spent learning AWS had finally paid off.
That evening, I sat on the couch with my laptop and took a moment to reflect on everything that had happened that day.
Passing the exam felt amazing, but I found myself thinking about something deeper.
What does this certification really mean to me?
What value did I gain from this journey?
How did I get here?
Was it worth six months of evenings and weekends?
As I thought through those questions, I realized the certification was more than just a badge.
It represented the hours spent learning, building, experimenting, making mistakes, and continuing to grow as an engineer.
Six months ago, I made a commitment to myself.
I was going to earn the AWS Certified Solutions Architect – Associate certification.
I also made one promise:
My study time would happen outside of work.
That meant evenings after work and weekends. I wanted this to be something I personally invested in.
My goal was simple:
Take the exam before the end of Q2 2026.
One hour at a time.
Day after day.
I watched courses on Pluralsight, filled notebooks with notes, and challenged myself to explain every concept in my own words.
I wasn't trying to memorize answers.
I wanted to understand why AWS services exist, when to use them, and the trade-offs behind each architectural decision.
One month passed.
Then two.
Then three.
Four.
Five.
Eventually, studying became part of my routine.
Some days were exciting because I discovered new services or architectural patterns.
Other days sent me down rabbit holes where learning one AWS service naturally led to three more.
Looking back, I realized preparing for the certification wasn't just about passing an exam.
It was about learning how to think like a solutions architect.
The practice exams—and especially the real exam—forced me to slow down and carefully evaluate every answer.
Many questions contained options that looked almost identical.
The challenge wasn't simply knowing what Amazon SQS or Amazon SNS does.
It was understanding why one service was the better architectural choice for that specific scenario.
That shift in thinking became one of the biggest lessons from the entire journey.
The certification validated my knowledge.
The learning process transformed the way I approach architecture decisions.
One thing I realized throughout this journey is that my day-to-day work doesn't always involve AWS.
That's exactly why pursuing this certification mattered so much.
It gave me the freedom to intentionally invest in learning AWS, experiment with new services, and deepen my understanding of cloud architecture outside of my regular responsibilities.
Since earning the certification, I've continued building serverless projects, experimenting with AI, writing technical articles, and finding new ways to apply what I've learned.
For me, this certification isn't the finish line.
It's another milestone in a much longer journey of continuous learning.
If you're looking for someone who's passionate about AWS, serverless architectures, AI, and building practical solutions, I'd love to connect.
Whether it's exchanging ideas, collaborating on projects, or discussing opportunities, feel free to reach out.
Looking back, earning the certification wasn't the hardest part.
The hardest part was showing up consistently, one hour at a time, for six months.
I'm grateful I made that commitment to myself.
"Because every difficult challenge we choose today becomes the confidence we carry into tomorrow."
What's your thought on this?
Top comments (1)
same, tbh.