Infrastructure as Code & Observability

Terraform state can contain values needed to manage infrastructure, including credentials returned by providers or passed into resources. Marking a variable as sensitive helps prevent casual display in output, but it does not guarantee the value is absent from state files, plans, logs, or provider-managed objects. Review where secrets enter the workflow...

Concurrent edits to shared infrastructure state can create lock contention, unclear ownership, or large plans with unrelated changes. Checks to make Define workspace and module ownership, require remote locking and reviewed plans, separate state by lifecycle boundary where appropriate, and document emergency procedures. Check state backups and avoid...

A module that works for one environment may encode assumptions about region, naming, permissions, or destructive defaults. Checks to make Review inputs, outputs, provider constraints, state behavior, IAM scope, lifecycle rules, and versioning. Test representative environments and failure cases, document safe defaults, and publish changes through a...

A remote state backend outage can block changes and recovery if state snapshots and access procedures are unclear. Checks to make Confirm versioning and backup retention, restrict access to recovery copies, document backend restoration steps, and test retrieval in a controlled workspace. Avoid running competing operations against manually copied state....

Sensitive values can appear in plan output, CI logs, state, or debug traces if providers and workflows handle them carelessly. Checks to make Mark sensitive variables, use an approved secret source, restrict plan and state access, and inspect CI log retention. Avoid printing environment values, rotate credentials if exposed, and confirm provider...

Automated plans help review infrastructure changes, but an unreviewed apply can create broad or destructive impact. Checks to make Generate a plan artifact tied to a commit, require authorized reviewers, flag destructive replacements, and ensure the applied plan matches the reviewed one. Restrict credentials and log the actor, target workspace, and...

Applying a valid plan to the wrong workspace can change an unrelated environment. Checks to make Make workspace and account identity visible in CI output, use separate credentials and state where appropriate, require environment-specific approval, and verify the planned resource addresses before apply. Add guardrails that fail when target metadata does...

Some infrastructure updates restart services, alter networking, or replace resources even when a plan appears routine. Checks to make Review provider behavior and replacement indicators, map affected dependencies and service impact, and compare change timing with business constraints. Mark maintenance needs in the review, notify owners, and test...