Terraform
Work with declared configuration, state, changes, secrets, approvals and recovery.
Learn the Terraform change workflow
Start with shared IaC concepts, then plan/apply/state and sensitive data. Fixed AWS examples require neither CDK knowledge nor an AWS account.
- Infrastructure as code explained: managing AWS configuration and changes →
- Terraform plan, apply and state: understanding the change workflow →
- Terraform sensitive data: protecting state and saved plans →
Compare when needed
Review management differences and adoption conditions.
Questions to guide your study
- Define its role: inputs, outputs and responsibility boundaries.
- Trace dependencies: required network, operating system, access and data conditions.
- Include operations: observable state, change impact and recovery procedures.
Available lessons and tools
Terraform plan, apply and state: understanding the change workflow
A plan proposes changes, apply performs planned operations, and state records how configuration maps to managed objects. “Change to 443 is proposed” and “the service works on 443” are different claims. Follow one edit while distinguishing files, records, current resources and execution results.
Terraform sensitive data: protecting state and saved plans
Marking a value sensitive redacts common displays; it does not guarantee that the value is never stored. Distinguish state, saved plans, explicit value output and CI artifacts. Trace where a value comes from, where it persists and who can read it.