You already know: the reconciliation loop (Kubernetes for ML); declarative serving deployments (Serving platforms); IAM and least privilege (Cloud fundamentals); testing and CI (D1 Testing & packaging); release gates (D10); versioning everything (D11).
Why this matters for Atlas. Infrastructure as code (IaC) describes infrastructure (networks, clusters, node pools, buckets, databases, IAM roles, DNS, Kubernetes deployments) in versioned text files, and uses tools to make reality match them. Every change becomes a reviewed pull request with a plan showing exactly what will change; environments (dev, staging, prod, another region) are created from the same code; and drift (manual changes that diverge from the code) is detected and corrected. Policy-as-code checks catch mistakes like public buckets before they're applied. This lesson builds the core mechanics: desired state, plans as diffs, state files, drift detection, modules for environments, GitOps, secrets and policy checks.
1. Declarative infrastructure and the plan
The question. Instead of clicking "create bucket", what does IaC do?
Start from nothing. You write the desired resources (Terraform/OpenTofu HCL, Pulumi in a general-purpose language, CloudFormation, Crossplane). The tool: