Rekindling lost AWS knowledge [AWS Cloud Practitioner Blog]

tldr; I'm just a regular guy trying to balance work and life while aiming for an AWS Cloud Practitioner certificate. How I got here I came across the Cloud Resume Challenge, and one of the suggestions there was to document the journey—so I decided to give dev blogging a try. Even though I already have my resume up at my own resume website, I figured—why not try to redo it on AWS? Right now, my website is built with simple React.js and hosted on Vercel. It was easy to set up and already serves as my current resume website. But then I thought—what's stopping me from rebuilding it in AWS? There's no rule or law that prevents me! So, why not? My previous AWS experience In my previous job, I was in charge of groups of developers. Aside from managing people, I also handled the tech—and most of it was hosted in AWS. Despite the small and limited scope, I was able to get hands-on with AWS tools that were given to me so that (1) we could observe the infrastructure, (2) suggest improvements to it, and (3) better understand it for future application architecture work. AWS Knowledge Stagnation Over the past few months, I’ve had the itch to dive back into AWS, but of course, the motivation didn’t really come—mainly because I don’t use it at all in my current work, and, let’s be honest, it can cost money. But hey, sometimes you gotta lose some (money) to gain some (knowledge). It’s just a small spend anyway—I'm just being stingy. Sure, I could do this on other platforms for free, but in my opinion, AWS is still a great tool to learn—especially since I get most excited when I’m working on application migrations. What can you expect should you choose to follow this series I know there are a ton of other series out there that guide you through learning AWS from scratch. If you're looking for a fast track, those are probably your best bet. I’m coming from the perspective of a "seasoned" developer who has other interests outside of programming. I recently moved to a foreign country and am learning a new language, while also living with my wife—whom I love deeply and want to spend as much quality time with as possible. I also want to keep an active lifestyle by going to the gym and hitting the trails. Basically, I'm just a regular family guy trying to stick to my principles of continuous learning, physical fitness, and enjoying life as it comes. I won’t go deep with full guides, but I’ll drop quick tips that cover 80% of real-world scenarios. I hope you enjoy reading my blog about my AWS journey—as a regular guy.

May 1, 2025 - 07:34

Rekindling lost AWS knowledge [AWS Cloud Practitioner Blog]

tldr;

I'm just a regular guy trying to balance work and life while aiming for an AWS Cloud Practitioner certificate.

How I got here

I came across the Cloud Resume Challenge, and one of the suggestions there was to document the journey—so I decided to give dev blogging a try.

Even though I already have my resume up at my own resume website, I figured—why not try to redo it on AWS?

Right now, my website is built with simple React.js and hosted on Vercel. It was easy to set up and already serves as my current resume website. But then I thought—what's stopping me from rebuilding it in AWS? There's no rule or law that prevents me! So, why not?

My previous AWS experience

In my previous job, I was in charge of groups of developers. Aside from managing people, I also handled the tech—and most of it was hosted in AWS.

Despite the small and limited scope, I was able to get hands-on with AWS tools that were given to me so that (1) we could observe the infrastructure, (2) suggest improvements to it, and (3) better understand it for future application architecture work.

AWS Knowledge Stagnation

Over the past few months, I’ve had the itch to dive back into AWS, but of course, the motivation didn’t really come—mainly because I don’t use it at all in my current work, and, let’s be honest, it can cost money.

But hey, sometimes you gotta lose some (money) to gain some (knowledge). It’s just a small spend anyway—I'm just being stingy. Sure, I could do this on other platforms for free, but in my opinion, AWS is still a great tool to learn—especially since I get most excited when I’m working on application migrations.

What can you expect should you choose to follow this series

I know there are a ton of other series out there that guide you through learning AWS from scratch. If you're looking for a fast track, those are probably your best bet.

I’m coming from the perspective of a "seasoned" developer who has other interests outside of programming. I recently moved to a foreign country and am learning a new language, while also living with my wife—whom I love deeply and want to spend as much quality time with as possible. I also want to keep an active lifestyle by going to the gym and hitting the trails.

Basically, I'm just a regular family guy trying to stick to my principles of continuous learning, physical fitness, and enjoying life as it comes. I won’t go deep with full guides, but I’ll drop quick tips that cover 80% of real-world scenarios.

I hope you enjoy reading my blog about my AWS journey—as a regular guy.