AWS Builder Center

Day 0: Starting My AWS Learning-in-Public Journey

I'm restarting my AWS learning journey with a focus on actually understanding the concepts, documenting what I learn, and building practical cloud skills along the way. This series will take me from revisiting Cloud Practitioner fundamentals to AI Practitioner and eventually Solutions Architect Associate.

Day 0: Starting My AWS Learning-in-Public Journey

I'm a Computer Science student specializing in Cloud Computing, and I'm about to do something I've been putting off for a while: document what I'm actually learning instead of quietly grinding through courses and forgetting half of it by the next module.

The Plan

Here's where I'm starting and where I want to go:

1. AWS Certified Cloud Practitioner

I've already cleared the certification, but it's been a couple of years, so I'm going back through the fundamentals properly.
This time, the goal isn't another certificate. It's making sure I actually understand the concepts behind the questions I answered the first time.

2. AWS Certified AI Practitioner

This is the certification I'm particularly excited about.
Generative AI on AWS, including services such as Amazon Bedrock and the broader AI/ML ecosystem, is an area I want to explore more deeply. I'm hoping this will give me a solid foundation before I start building more practical AI-powered applications.

3. AWS Certified Solutions Architect – Associate

This is probably the biggest goal of the three.
I don't just want to know what AWS services do. I want to understand when and why to use them, how they fit together, and how to design architectures that can actually handle real workloads.

How I'm Learning

I'm working through Stephane Maarek's courses for Cloud Practitioner and Solutions Architect Associate, while using AWS Skill Builder for additional learning, interactive content, and hands-on practice.
For AI Practitioner, I'll be relying more heavily on AWS's own Skill Builder material since this is newer territory for me.

Why Learn in Public?

There are two main reasons.
First, revisiting a certification I already passed gives me a chance to find the gaps that didn't show up on exam day. Trying to explain something back, even if nobody reads it, makes it pretty obvious when I only thought I understood something.
Second, I'm entering the fresher job-search phase, and I think having a public record of what I'm learning and building is much more valuable than simply having a list of certifications on a resume.

What to Expect

These won't be polished AWS tutorials.
I want these posts to be short, honest updates about what I'm learning — including the things I get wrong, the concepts that finally click, and the practical lessons I pick up along the way.
Some posts might be about something I thought I understood but actually didn't.
Others might be about a small AWS concept that finally made sense after seeing it in practice.
I'd rather share something useful and genuine than spend hours trying to make every post perfect.
So this is Day 0. Let's see where this goes. ☁️
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