My Cloud Engineering Roadmap ☁️⚙️
Starting a journey into Cloud Engineering can quickly become overwhelming.
There are countless tools, technologies, certifications, courses, and roadmaps available. After spending time researching different learning paths and consulting with people in the field, I realized I needed something more focused — a roadmap that would give me direction without trying to learn everything at once.
So, I designed my own Cloud Engineering Roadmap.
�
The Roadmap
I've structured my learning into six phases:
Phase 1 — Linux, Networking & Git
Building the foundational skills I'll need to work with cloud infrastructure.
Phase 2 — Core Cloud & AWS
Learning the fundamentals of cloud computing and focusing on AWS, including VPC, IAM and the AWS CLI.
Phase 3 — Infrastructure as Code
Learning Terraform and understanding how to provision and manage infrastructure as code.
Phase 4 — Python for Cloud Automation
Learning enough Python to automate tasks and interact with AWS through boto3.
Phase 5 — Containers & CI/CD
Working with Docker, CI/CD pipelines, GitHub Actions and eventually Kubernetes.
Phase 6 — Observability, Cost & Security
Learning how to monitor infrastructure, manage cloud costs and apply security practices.
Why This Approach?
I don't want to simply collect certificates or finish courses.
I want to understand what I'm learning, practice it, build projects, and document my progress.
I'm also intentionally keeping the roadmap focused. There are many technologies I could add, but I've learned that trying to learn everything at once can easily lead to information overload.
This roadmap is therefore not meant to be a universal Cloud Engineering roadmap. It's the learning path I've designed for myself based on my current goals and research.
And I expect it to change.
As I gain more practical experience, I may add, remove, or reorder things based on what I discover along the way.
What's Next?
I'm taking the self-taught route into Cloud Engineering, and I'm excited to see where it leads.
My approach is simple:
Learn → Practice → Build → Document → Repeat.
I'll be sharing what I learn, the projects I build, the challenges I encounter, and hopefully some lessons that can help others on a similar journey.
If you're already working in Cloud, DevOps, SRE, or Platform Engineering, I'd love to hear your thoughts.
What would you change about this roadmap?
I'm open to learning. 🚀
Top comments (1)
Putting Python/boto3 automation before Kubernetes is a smart order, most roadmaps front-load container orchestration before you've even scripted anything against a cloud API. The learn-practice-build-document loop will serve you better than chasing certificates too. Good luck with it.