Skip to main content
2026 Edition · From your first deploy to a platform

How the cloud is
actually run.

A complete path into cloud engineering. Start at "what even is a region?" and end able to design, provision, ship, observe and secure real infrastructure — across AWS, GCP and Azure, with the durable concepts foregrounded so the skills outlast any one tool. Every term is defined the first time it appears.

11
Chapters
AWS · GCP · Azure
Big-3, side by side
Jun ’26
Last reviewed
$0
Free · source-available
main.tfapply
# Infrastructure described as code, not clicked in a console.
resource "aws_s3_bucket" "site" {
  bucket = "my-app-assets"
  tags  = { env = "prod" }
}

# → Plan: 1 to add, 0 to change, 0 to destroy.
declarative · versionedreviewable like any code
Start here

Two ground-truth facts before chapter 1.

01

The cloud is just someone else's computers — rented by the second, run by API.

Every service is, underneath, a server, a disk, or a network the provider owns and you rent on demand. Master that mental model and the hundreds of branded products collapse into a handful of primitives you already understand.

02

Learn the durable concept, not the dated console.

Buttons move and products get renamed every year. But compute, object storage, identity, and declarative infra are decades-stable. This guide teaches the concept first, then shows it in AWS, GCP and Azure.

Who it’s for

Meets you wherever you are.

“I can write code…”
…but I’ve never provisioned a server, and the AWS console terrifies me. Start at region one — no prior ops experience assumed.
“I run production infra.”
…and want a sharp 2026 refresh on IaC, Kubernetes, platform engineering, FinOps and the decision rules that actually hold up.
Ready?

What happens when you click "Deploy"?

The whole guide fans out from that one question. Twenty minutes from now you’ll know exactly what a region, an availability zone, and the shared-responsibility model are — and why every later decision rests on them.