Infrastructure as code as governance
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
require reviewed infrastructure as code (IaC) for every environment.
Planned topics
- Infrastructure defined as code is versioned, reviewable, and repeatable.
- Changes go through pull request, review, automated checks, and a pipeline; manual console changes are blocked or detected.
- Policy checks run in the pipeline before deployment.
- Drift detection compares reality to code.
- Separate roles: pipeline deploys to prod; people have read access by default.
Draft outline details
Demonstration
a pipeline: pull request, review, static policy checks, plan, approval, apply, drift check.
Check your understanding
Why restrict console changes in prod?
Show answer
They bypass review and cannot be reproduced or audited easily.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.