𝐖𝐡𝐲 𝐰𝐨𝐮𝐥𝐝 𝐚 𝐜𝐥𝐨𝐮𝐝 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭 𝐠𝐨 𝐛𝐚𝐜𝐤 𝐭𝐨 𝐭𝐡𝐞 𝐛𝐞𝐠𝐢𝐧𝐧𝐢𝐧𝐠?

After some time working on cloud architectures and implementations in AWS, leading projects in regulated sectors, I made a decision that might seem contradictory: Going Back to the Beginning. Yes, I chose to revisit my foundations through the AWS Certified Cloud Practitioner.

Not because of a lack of technical knowledge. Not because of external pressure. But for something deeper: to reorganize my experience, reconnect with core concepts, and translate what I know into a language that resonates with those just starting out.

Along the way, I’ve discovered that:

• Understanding basic services like IAM from scratch pushes me to reassess cloud security with clarity.
• Reviewing virtual machines, storage, and databases helps me teach through real-world examples, not jargon.
• Studying Pricing and Billing connects me with FinOps and strategic decision-making.

Going back to the beginning isn’t a step backward. It’s rebuilding with purpose, humility, and a vision for impact.

I’m exploring this path through the end of the year, sharing whatever comes up: hands-on practices, open reflections, and insights I find useful.

If you’re starting out in AWS, or if you’re reorganizing your own cloud journey, maybe something I share will be helpful.

There’s no fixed schedule or big promises. Just a genuine desire to build from what’s real. And if I pause at any point, that too will be part of the process. Because this isn’t about perfection—maybe it’s about honest evolution.