Infrastructure as Code stores desired infrastructure configuration in reviewable files. A small text change can still create, replace, expose, or delete real resources, so planning and review are essential.
Read the plan
Check every create, update, replacement, and deletion. Consider cost, network exposure, identity changes, dependencies, and whether an operation affects persistent data.
Protect state
State helps map configuration to managed resources. Use the documented backend and access controls, and avoid committing state or credentials into public repositories. Investigate unexpected drift before trying to force a change.
Use least privilege and approvals
Use scoped identities, protected environments, and required review for sensitive changes. Practice only in an approved sandbox with a cleanup plan and known budget controls.
Provider behavior and tooling versions can change. Verify current documentation before applying real infrastructure changes.