How much Cloud & DevOps do you already have?
Be honest — nobody is watching. This only decides which chapters come first; every chapter stays open to you either way.
“I can deploy a working app to the cloud.”
Start with what "the cloud" actually is — compute, storage, networking, IAM — and get a small app deployed and reachable.
- You've deployed to something like Vercel/Netlify but not a raw cloud provider
- EC2, S3 and IAM are names you've seen, not things you've configured
- You want the building blocks once, in order, before Terraform and pipelines
“I can run a real service in the cloud.”
You can deploy an app. Now learn what a real service needs: a managed database, autoscaling, IaC, and a pipeline that ships changes safely.
- Comfortable deploying a single app manually
- You've clicked through a console to change something and known it wasn't repeatable
- You want infrastructure defined as code, and a pipeline you trust
“I can architect for real scale.”
Multi-region availability, container platforms, and the security/cost decisions behind a cloud footprint that spans an organization.
- You can already ship a service via IaC and a real pipeline
- You debug regional outages and IAM edge cases, not just deploy failures
- You want the why under multi-account strategy and disaster recovery
Not sure? Start at Beginner — every path opens at the section people usually skip.
Full syllabus
Everything each level eventually covers — ticked sections are written, the rest are still on the desk.
Beginner0 / 7 sections written
- Cloud computing fundamentalscoming soon
IaaS/PaaS/SaaS, why cloud at all
- Compute basicscoming soon
EC2/VMs vs serverless functions
- Storage basicscoming soon
Object storage (S3), block storage, when to use each
- Networking basicscoming soon
VPCs, subnets, security groups — surface level
- IAMcoming soon
Users, roles, policies, least privilege
- Deploying a simple appcoming soon
Putting it together end to end
- The cloud provider landscapecoming soon
AWS vs GCP vs Azure — picking one
✅ Checkpoint: you can deploy a small app to a cloud VM or serverless function yourself, with the right IAM role and no exposed secrets.
Intermediate0 / 9 sections written
- Managed databasescoming soon
RDS-style managed Postgres/Mongo, backups
- Load balancers & auto-scalingcoming soon
Distributing traffic, scaling with demand
- Serverless in depthcoming soon
Lambda/Cloud Functions, triggers, cold starts
- Infrastructure as Codecoming soon
Terraform/CloudFormation basics
- CI/CD pipelines in the cloudcoming soon
A deploy pipeline, end to end
- Monitoring & loggingcoming soon
CloudWatch/Cloud Logging basics
- Environments & configcoming soon
Dev/staging/prod, secrets in the cloud
- CDN & edgecoming soon
CloudFront/Cloud CDN
- Cost managementcoming soon
Reading a cloud bill, avoiding surprises
✅ Checkpoint: you can stand up a load-balanced, autoscaled service with a managed database, defined in Terraform, deployed by a CI/CD pipeline.
Advanced0 / 8 sections written
- Multi-region & high availabilitycoming soon
Designing for a region going down
- Container servicescoming soon
ECS/Fargate/Cloud Run — the bridge to Kubernetes
- Advanced IAMcoming soon
Cross-account roles, federated identity
- Disaster recoverycoming soon
Backup strategy, RTO/RPO
- Observability at scalecoming soon
Distributed tracing in the cloud
- Security in the cloudcoming soon
Shared responsibility model, encryption at rest/transit
- Landing zones & multi-account strategycoming soon
Organizing many accounts/projects at scale
- FinOpscoming soon
Optimizing cost at scale
✅ Checkpoint: you can design a multi-region, highly-available architecture, defend a disaster-recovery plan (RTO/RPO), and explain the shared-responsibility model.
- IAM shows up in beginner as "the four ideas you need" and again in advanced as "cross-account, federated, at scale" — access control is the thing that quietly causes the worst incidents either way.
- This deliberately bridges into Docker and Kubernetes rather than re-teaching them — containers-as-a-service (ECS/Cloud Run) is the advanced chapter's bridge, not a rebuild of either curriculum.
- FinOps and multi-account strategy are the deepest, most organization-shaped layer — most individual developers never own them, but the advanced tier doesn't skip them.