AWS Builder Center

Aws journey

My AWS Builder Journey: 21 Badges, Continuous Learning, and the Road to My AWS Voucher

As a software engineer, I have always believed that the best way to learn technology is by building with it.
Reading documentation is important. Watching courses is valuable. But nothing compares to actually getting your hands dirty, solving problems, making mistakes, debugging them, and understanding why a solution works.
That mindset led me to start my AWS Builder journey.
My initial goal was simple: explore AWS, strengthen my cloud knowledge, and challenge myself to complete the activities available through the AWS Builder ecosystem. What started as a learning goal quickly became a personal challenge: earn 21 badges and work toward the AWS certification voucher.
Starting the Journey
Coming from a software engineering background, I already had experience with application development, APIs, databases, CI/CD, testing, and enterprise systems.
However, cloud computing requires a different way of thinking.
It is not only about writing code. It is about understanding how applications are deployed, secured, scaled, monitored, and integrated with infrastructure.
AWS introduced me to a broader perspective of software engineering:
  • Compute and serverless architectures
  • Storage
  • Databases
  • Networking
  • Security and IAM
  • Monitoring and observability
  • DevOps and CI/CD
  • Cloud architecture
  • Cost optimization
  • Scalability and reliability
Each Builder activity became an opportunity to connect these concepts with problems I encounter as a software engineer.
The 21-Badge Challenge
One of the most motivating parts of the journey was turning learning into a measurable challenge.
Instead of simply saying:
“I want to learn AWS.”
I gave myself a concrete objective:
21 badges.
Every badge represented another step forward.
Some activities were straightforward. Others required more investigation, experimentation, and persistence. There were moments when something didn’t work as expected, and that was actually one of the most valuable parts of the experience.
Software engineering is rarely about everything working perfectly on the first attempt.
The real learning happens when you ask:
Why did this fail?
Then you investigate.
You read the documentation.
You test a hypothesis.
You change the implementation.
You try again.
And eventually, it works.
That same engineering mindset applies directly to cloud learning.
Learning by Doing
The AWS Builder experience reinforced something I already knew from software development: practical experience is incredibly powerful.
Instead of memorizing what a service does, I could interact with it and understand where it fits in a real architecture.
For example, understanding the difference between compute, storage, databases, networking, and serverless services becomes much easier when you actually see how they interact.
The cloud stops being a collection of service names and starts becoming an architecture.
That shift in perspective has been one of the most important outcomes of my journey.
Badges Are More Than Badges
At first, the number 21 was simply a target.
But along the way, I realized that the badges themselves weren’t the most important achievement.
The real achievement was the knowledge accumulated behind them.
Every badge represents:
  • Time invested in learning
  • Problems solved
  • Concepts explored
  • Documentation read
  • Experiments performed
  • Mistakes corrected
  • New AWS services understood
For me, the badges became checkpoints in a much larger learning journey.
They provided motivation, but the knowledge is what stays.
The Software Engineer Perspective
Cloud knowledge is becoming increasingly important for software engineers.
Modern applications rarely live entirely inside a single server.
Applications are distributed.
They communicate through APIs.
They use managed databases and storage.
They rely on authentication and authorization.
They require monitoring.
They need automated deployments.
They must scale.
And they need to remain secure and reliable.
Understanding cloud architecture therefore makes me a better software engineer, even when I’m writing application code.
AWS has helped me think beyond the implementation of a single class, endpoint, or service and consider the complete lifecycle of an application.
From development to deployment.
From infrastructure to observability.
From security to scalability.
That broader perspective is something I can take back into my everyday engineering work.
The Voucher Goal
There is also another motivation behind this journey: the AWS certification voucher.
Earning the voucher represents more than saving money on an exam.
It represents an opportunity to turn the knowledge gained through the Builder journey into a formal certification.
My objective is to continue studying, complete the required activities, strengthen my fundamentals, and eventually take the certification exam with confidence.
The voucher is the incentive.
The learning is the real reward.
What I Learned Along the Way
If I had to summarize the biggest lessons from this journey, they would be:
  1. Consistency beats intensity
You don’t need to learn everything about AWS in one week.
A little progress every day compounds.
  1. Build instead of only watching
Hands-on experience creates a much deeper understanding than passive learning.
  1. Documentation is part of engineering
Being comfortable reading technical documentation is one of the most important skills a software engineer can develop.
  1. Failure is part of the process
A failed lab, an incorrect configuration, or an unexpected error isn’t wasted time.
It’s feedback.
  1. Certifications are milestones, not destinations
A certification validates knowledge, but continuous learning is what keeps that knowledge relevant.
What’s Next?
Completing 21 badges is an important milestone, but I don’t see it as the end of the journey.
It is the beginning of the next stage.
My next objectives are to deepen my understanding of AWS architecture, continue practicing with hands-on labs, strengthen my knowledge of cloud security and scalability, and prepare for the certification exam.
Eventually, I want to look back at these 21 badges and see them not as individual achievements, but as the first chapters of my cloud engineering journey.
Final Thoughts
Every software engineer has a different way of learning.
For me, the most effective approach has always been to combine theory with practice.
The AWS Builder journey gave me exactly that opportunity.
21 badges.
One certification goal.
Hundreds of concepts to explore.
And, most importantly, a continuous reminder that technology is something we learn by building.
The AWS voucher is a great incentive, but the bigger achievement is becoming a better engineer along the way.
This journey isn’t finished yet.
I’m still building.
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