How to use the Cloud Engineer Roadmap
- 1. Tick what you knowOpen each stage and tick the topics you can already do confidently.
- 2. Pick your paceChoose how many hours a week you can study; the estimate updates for what's left.
- 3. Get your planSee time left per stage and your next three topics, and download the checklist.
Who this roadmap is for
Cloud engineers design, build and run infrastructure on platforms like AWS, Azure and Google Cloud. This roadmap starts with Linux and networking, because almost every cloud problem (a server you can't reach, a database timing out) comes down to them.
Choose one provider and go deep; the ideas transfer. A virtual network, a role, a bucket and a managed database exist on every major cloud under different names.
The 8 stages
Each of the 8 stages of the Cloud Engineer path ends with a milestone project, because building something is what turns topics into skills.
- Linux and networking (about 4 weeks): Linux commands, files, permissions and processes, Shell scripting basics, Networking: IP, subnets, DNS, ports, TCP vs UDP and more. Milestone: Set up a Linux server, harden SSH and host a static site.
- One cloud provider (about 5 weeks): Core services: compute, storage, networking, IAM (AWS, Azure or GCP), Virtual networks, subnets and security groups, Object storage and static hosting and more. Milestone: Host a web app on a VM with a managed database inside a private subnet.
- Identity and security (about 2 weeks): Least-privilege IAM policies and roles, MFA, SSO and avoiding long-lived keys, Encryption at rest and in transit and more. Milestone: Write and test least-privilege policies for your app.
- Infrastructure as code (about 3 weeks): Terraform basics: providers, resources, state, Variables, modules and remote state, Plan and review changes safely and more. Milestone: Recreate your app's infrastructure in Terraform from scratch.
- Containers (about 4 weeks): Docker images, layers and registries, Docker Compose for local stacks, Kubernetes basics: pods, deployments, services and more. Milestone: Run the app on a managed Kubernetes cluster.
- CI/CD and automation (about 2 weeks): Pipelines with GitHub Actions or GitLab CI, Build, test and deploy stages, Blue-green and rolling deployments and more. Milestone: Pipeline that deploys on every merge to main.
- Monitoring and reliability (about 2 weeks): Logs, metrics and alerts, Health checks and auto scaling, Backups and disaster recovery and more. Milestone: Dashboard and alerts for your app; test a restore from backup.
- Certification and job ready (about 3 weeks): An associate-level certification for your chosen cloud, Architecture diagrams for your projects, Interview topics: networking, IAM, scaling and more. Milestone: Write up one project as an architecture case study.
How the time estimate works
Worked example: with nothing ticked and 10 hours a week, the plan shows about 25 weeks for all 34 topics. Choose 20 hours a week and it becomes about 12.5 weeks. Tick every topic in the first stage, Linux and networking, and that row shows "done" while the total at 10 hours a week drops by 4 weeks to about 21.
Week counts are our suggestion for steady self-study of the Cloud Engineer path, based on how much each stage covers. They are not survey data or a promise; use them to plan, not to judge yourself.
Tips for following it
- Set a billing budget and alert on day one; forgotten lab resources are the most common surprise bill.
- Write everything in Terraform once you reach that stage, even small experiments.
- Draw an architecture diagram for each project; interviewers ask you to explain design choices.
Frequently asked questions
AWS, Azure or Google Cloud?
Pick the one most common in the jobs you're targeting. Skills carry over; certifications don't.
Is certification enough?
Certifications help you get noticed, but interviews test hands-on labs and troubleshooting. The milestones give you those stories.
Where are my ticks saved?
Your Cloud Engineer Roadmap ticks are kept only in this browser on this device, so nothing you tick is sent anywhere. Clearing site data or switching browsers starts you fresh; download your checklist to keep a copy.
Is the Cloud Engineer Roadmap free?
Yes. Reading the Cloud Engineer Roadmap and ticking topics is open to everyone. Viewing your plan the first time asks for your name and WhatsApp number once; after that every Uncodemy tool is free and open to you.