Why Cloud Engineering?
The infrastructure skill set behind almost every modern product
Almost nothing ships on-prem anymore. Startups and enterprises alike run their applications on AWS, Azure, or Google Cloud, which means someone has to design the virtual networks, provision the compute and storage, lock down access, and keep the whole thing running without falling over — or blowing the budget. That's the Cloud Engineer: part infrastructure architect, part security-minded operator, fluent in the specific services of at least one major provider and the patterns (autoscaling, high availability, disaster recovery) that make cloud systems resilient.
It's a strong, durable career path precisely because cloud spend keeps growing and the skill gap hasn't closed — provider certifications (AWS, Azure, GCP) are some of the most recognized credentials in tech, and the role has real overlap with DevOps and Data Engineering once you add automation and pipelines into the mix. The roadmap below covers the core path: fundamentals first, then one provider deeply, then the security, automation, and cost-control layers that separate a working cloud setup from a production-grade one.
Choosing a Cloud Provider
The services differ in name, the underlying concepts below don't
AWS
The largest market share and service catalog — the safest default for job opportunities and community support.
Microsoft Azure
Common in enterprises already invested in Windows Server, Active Directory, and the Microsoft ecosystem.
Google Cloud
Strong in data analytics, machine learning, and Kubernetes — the platform Google open-sourced in the first place.
Multi-cloud
Using more than one provider at once — worth understanding conceptually, but not where beginners should start.
Getting Started
Free-tier accounts are enough to work through this entire roadmap
Every major provider offers a free tier — create an AWS, Azure, or Google Cloud account (a credit card is required for verification, but the core services in this roadmap fit comfortably within free-tier limits if you remember to tear resources down after each lesson). Set a billing alarm on day one so you get notified before any surprise charges.
For a local workflow, install the provider's CLI (aws, az, or gcloud) alongside VS Code, and get comfortable with a terminal — nearly every step in this roadmap, from Linux basics through Terraform, happens at the command line rather than by clicking through a console.
None of this requires paid tools or a powerful machine — a free provider account, a free editor, and a terminal are enough to work through every step below.
Quick intro — what is Cloud Engineering?
A quick primer before you start the roadmap. Opens in a small player, no need to leave the page.
The Cloud Engineer Roadmap
Pick a level — each one includes everything from the levels before it
Steps 1 – 4: cloud fundamentals, networking, Linux, and picking a provider
Cloud Computing Fundamentals
IaaS vs PaaS vs SaaS, public/private/hybrid deployment models, elasticity, and the shared responsibility model between you and your provider.
Networking Fundamentals
DNS, IP addressing and subnetting, virtual networks (VPC/VNet), load balancers, and CDNs — the plumbing every cloud service sits on top of.
Linux & Command Line Basics
Shell navigation, permissions, process management, and scripting — nearly every cloud instance you'll touch runs Linux under the hood.
Pick a Cloud Provider
Go deep on one major provider — AWS, Azure, or Google Cloud — and learn its console, CLI, resource hierarchy, and regions/availability zones.
Compute Services
Virtual machines (EC2, Azure VMs, Compute Engine), serverless functions (Lambda, Azure Functions, Cloud Functions), and when to pick each.
Storage & Databases
Object storage (S3, Blob Storage, Cloud Storage), block storage, and managed databases (RDS, Cloud SQL, DynamoDB) for different data needs.
Identity, Access & Security
IAM users, roles, and policies, the principle of least privilege, encryption at rest and in transit, and cloud-native security tooling.
Infrastructure as Code
Define and version your infrastructure instead of clicking through a console, with Terraform, AWS CloudFormation, or Azure Bicep/ARM.
Containers & Orchestration
Package applications with Docker and run them at scale with managed Kubernetes — EKS on AWS, AKS on Azure, or GKE on Google Cloud.
CI/CD & Automation
Automate builds, tests, and deployments with GitHub Actions, GitLab CI, Jenkins, or provider-native pipelines like AWS CodePipeline.
Monitoring & Logging
Track health and performance with CloudWatch, Azure Monitor, or Grafana/Prometheus, and centralize logs so incidents are fast to diagnose.
Cost Optimization & Certifications
Right-sizing, reserved/spot instances, tagging for cost visibility, and provider certifications (AWS Solutions Architect, Azure Administrator, GCP ACE) to validate what you've learned.
Cloud & DevOps Practice Exercises
Drill Linux, networking, and core cloud concepts with a huge bank of practice questions and exercises, matching steps 1 – 4.
Provisioned VPC & Compute
Use Terraform to stand up a VPC, subnets, and an EC2 instance, then tear it all down cleanly with a single command.
Serverless Application
Deploy a full serverless app using Lambda, API Gateway, and DynamoDB to see event-driven architecture in practice.
Kubernetes the Hard Way
Build a Kubernetes cluster from scratch, node by node, to understand exactly what a managed service like EKS is doing for you.
Cloud Monitoring Stack
Deploy Prometheus and Grafana against a cloud workload and build a dashboard that tracks real infrastructure metrics.
AWS Certified Cloud Practitioner
An entry-level, vendor-neutral-in-spirit credential covering cloud concepts, core AWS services, security, and billing — a solid check on steps 1 – 4 of this roadmap.
Learn moreAWS Certified Solutions Architect – Associate
Validates the ability to design available, cost-efficient architectures using compute, storage, databases, and IAM — a natural checkpoint after steps 1 – 8, once IaC is in place.
Learn moreAWS Certified DevOps Engineer – Professional
A professional-level credential covering CI/CD, containers, monitoring, and operational excellence at scale — matching the full roadmap, steps 1 – 12.
Learn moreCommunity & Support
Where to ask when a step doesn't click
Stack Overflow
Best for specific, well-defined technical questions with searchable, vetted answers.
r/aws & r/devops
Casual, active discussion on providers, architecture, and getting started, aimed at working engineers.
AWS re:Post
AWS's own Q&A community, staffed in part by AWS experts, for service-specific troubleshooting.
freeCodeCamp Forum
Beginner-friendly help tied directly to the certifications this roadmap targets.
Frequently Asked Questions
Common questions from people starting out in cloud engineering
Is cloud engineering hard to learn?
The console-clicking basics are approachable fairly quickly, but building real intuition for networking, security, and cost trade-offs takes longer and mostly comes from actually provisioning infrastructure — ideally with Infrastructure as Code — rather than reading service docs alone.
AWS vs. Azure vs. Google Cloud — which should I learn first?
AWS has the largest market share and job market, making it a safe default. Azure shows up heavily in enterprises already using Microsoft tools, and Google Cloud is strong in data and ML-heavy shops. The underlying concepts — VPCs, IAM, managed databases — transfer between all three, so picking one and going deep matters more than which one you pick.
Do I need to know how to code to become a Cloud Engineer?
You don't need to be a software engineer, but you do need to be comfortable scripting — Bash for automation, HCL for Terraform, and enough YAML/JSON to read and write configuration files and CI/CD pipelines fluently.
Which certification should I get first?
The AWS Certified Cloud Practitioner (or Azure/GCP's equivalent fundamentals exam) is the standard starting point — it's broad rather than deep, and confirms you understand core cloud concepts before moving on to a role-based Associate certification like Solutions Architect.
How do I prepare for a Cloud Engineer interview?
Be fluent in core networking (VPCs, subnets, security groups), IAM fundamentals, and at least one IaC tool. Be ready to whiteboard a simple, highly-available architecture, explain the shared responsibility model, and talk through a real cost or incident you diagnosed if you have hands-on project experience to draw on.
Track complete
Twelve steps, from cloud fundamentals to cost-optimized, certified infrastructure. Push what you built to GitHub so it's visible to employers, then keep going — cloud is learned by provisioning real infrastructure, not just reading service docs.
Related Roadmaps
Where cloud engineering skills lead next
DevOps Roadmap
Extend the CI/CD and automation concepts from step 10 into full DevOps practice.
Data Engineer Roadmap
Go deeper on the storage and database services introduced in step 6.
AWS Roadmap
Go deeper on the provider introduced in step 4.
Terraform Roadmap
Focus in on the Infrastructure as Code from step 8.
Kubernetes Roadmap
Go deeper on the container orchestration introduced in step 9.
Security Engineer Roadmap
Extend the IAM and security concepts from step 7 into a dedicated security track.
Where next?
Keep exploring by domain or drill into a single skill — or continue on to DevOps and Data Engineer