water park

Course 2 · after Fountain

The IAM repo

Context

Intro

Fifteen lessons build an access repo from nothing and then hand it to an agent.

The first six are the shape. One resource per file and the path as the index, personas and principals so a leaf file is a call and a list of grants, the guardrails in the editor that CI runs unchanged, a deploy with no account at all, the boundary every role stands inside, and one path to prod with a job that refuses a plan whose digest is not the one a reviewer approved.

Then the parts that only matter once something is live. Drift, where the account moved and the repo did not. Delegation, where a satellite repo owns its own files and gets refused twice if it reaches further. Federation, so nothing holds a static key. Break-glass, where access is granted in a hurry and expires on its own. Offboarding and the access review, which is the artifact somebody outside the team will accept.

The last four put the agent on it. The concierge takes a request in plain words and opens a pull request you can read, and refuses one from somebody the estate has never heard of. The watcher runs with nobody in the room and files what it finds under rules that hold when its prompt is ignored. Approve the change and not the diff is the digest that binds an approval to a change rather than to a run. And walking away is adopting what already exists without changing it.

The estate is real, the checks run on every push, and the repo you cloned to take the course is the repo the course manages.

15 lessons · about 10 h 35 min self-paced

  1. 1 One resource per file The repo is Terraform with one resource per file. · 40 min I P1P2 I1
  2. 2 Personas and principals Humans get permission sets and workloads get roles. · 45 min V P2P3 I2
  3. 3 Guardrails in the editor The guardrails run in the editor, for the agent and in the PR job alike. · 45 min II P4 I3
  4. 4 Deploy to Floci The estate deploys to Floci with no account. · 30 min XII P6 (part) I4
  5. 5 The permission boundary The permission boundary caps every role and the apply role itself. · 45 min VIIII P7 I5
  6. 6 One path to prod The PR is the only path to the estate. · 75 min IVIXXIVII P5P6P7 I6
  7. 7 Drift A scheduled plan detects drift and a PR restores the declared state. · 35 min XIXIII P11 I7
  8. 8 Delegation and the double refusal A satellite may create roles only inside the boundary, checked twice. · 50 min VI P8P10 I8
  9. 9 Federation trust Trust policies are declared resources with the strictest checks. · 40 min XV P12 I9
  10. 10 Break-glass Break-glass access expires cloud-side whatever else fails. · 40 min VIIVIII P9 I10
  11. 11 Offboard and the access review Offboarding removes every reference in one PR and the review reads the estate. · 35 min IXXIII I11
  12. 12 The concierge The AWS desk turns a request into a one-file PR. · 45 min VVIIIIX P13 I12
  13. 13 The watcher The desk on a schedule turns findings into capped PRs. · 40 min XIII I13
  14. 14 Approve the change, not the diff The reviewer approves a plan and its digest, and the apply refuses anything else. · 35 min VIIIXIVVII P14 I14
  15. 15 Adopt in place An import block brings what already exists under management, one file at a time, and changes nothing about it. · 35 min IXII I15