Skip to main content
Technology & EngineeringDevOps Cloud31 lines

Review Infrastructure Plans for Impact and Cost

Review Terraform plans, Pulumi previews and CloudFormation change sets for replacements, drift, security, blast radius and cost.

Quick Summary9 lines
Record the tool and version, commit, target account and environment, stack or workspace, provider settings and input revision. Use the project’s supported review artifact: Terraform plan, Pulumi preview, or CloudFormation change set. CloudFormation-based CDK work also needs the generated template or change set for its target. Confirm that the artifact was generated from the source under review and is recent enough for the environment. Restrict access because raw plan output can contain sensitive information.

## Key Points

- [Terraform plan command](https://developer.hashicorp.com/terraform/cli/commands/plan)
- [Pulumi preview](https://www.pulumi.com/docs/iac/cli/commands/pulumi_preview/)
- [CloudFormation change sets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-changesets.html)
skilldb get devops-cloud-skills/infrastructure-change-reviewFull skill: 31 lines
Paste into your CLAUDE.md or agent config

Review Infrastructure Plans for Impact and Cost

Bind the plan to the change

Record the tool and version, commit, target account and environment, stack or workspace, provider settings and input revision. Use the project’s supported review artifact: Terraform plan, Pulumi preview, or CloudFormation change set. CloudFormation-based CDK work also needs the generated template or change set for its target. Confirm that the artifact was generated from the source under review and is recent enough for the environment. Restrict access because raw plan output can contain sensitive information.

Compare expected changes with actual resource actions. Review replacement and deletion individually even when the action totals are small. Include dependent resources, downstream clients, and ordering. A storage replacement may affect retained data, and a network replacement may change service endpoints. Identify recovery prerequisites and service owners. A preview artifact does not prove the provider will accept or successfully apply every action.

Separate drift, posture, and cost

Identify current drift using the tool’s documented read or preview behavior. Establish whether the drift is an approved live change, a stale local assumption, an unmanaged resource, or unexplained. Record which state or inventory evidence was actually checked. Avoid mutating state or importing resources as a side effect of reviewing a plan.

Review effective access, public exposure, network rules, encryption, retention and ownership tags on changed resources. Look at resulting values and inherited defaults rather than relying on a module name. Check whether new privileges are scoped to the workload. Record unresolved values the preview cannot compute. Use policy checks where supported and inspect exceptions against ownership and scope.

Estimate likely recurring and one-time cost changes using documented units, region, expected utilization and service dependencies. State cost assumptions and unknowns. Replacement can cause a temporary overlap charge or a migration fee. A cost tool’s partial result should remain partial in the review.

Produce the decision and evidence

For each material finding list resource identity, action, blast radius, source artifact and acceptance condition. Distinguish the need for a new preview, owner approval, recovery evidence, security correction or cost confirmation. Re-run the review after changes to the artifact or target. Verify a known fixture with one high-impact replacement and one privilege expansion, and a second fixture with drift or unresolved values. Keep plan approval separate from executing the infrastructure change.

References

Install this skill directly: skilldb add devops-cloud-skills

Get CLI access →

Related Skills

Monitoring Observability

Build observability systems using metrics, logs, and traces to understand system behavior and diagnose issues. Trigger keywords: monitoring, observability, metrics, logging, tracing, Prometheus, Grafana, Datadog, alerting, SLO, SLI.

DevOps Cloud•71L

Security Devops

Integrate security practices into DevOps workflows and CI/CD pipelines. Covers shift-left security, vulnerability scanning, and secure development lifecycle. Trigger keywords: DevSecOps, security automation, vulnerability scanning, SAST, DAST, supply chain security, shift-left.

DevOps Cloud•147L

Service Mesh

Implement service mesh infrastructure for managing microservice communication, observability, and security. Trigger keywords: service mesh, Istio, Linkerd, Envoy, sidecar proxy, mTLS, traffic management, circuit breaker.

DevOps Cloud•153L

Web Infrastructure Basics

Understand DNS, domain management, CDNs, SSL/TLS, load balancing, and web hosting fundamentals. Use this skill when the user asks about setting up a domain, configuring DNS records, understanding how websites are served, choosing hosting, setting up HTTPS, or troubleshooting domain and DNS issues.

DevOps Cloud•111L

CI CD Pipelines

Design and maintain continuous integration and continuous delivery pipelines that automate build, test, and deployment workflows. Trigger keywords: CI/CD, pipeline, GitHub Actions, Jenkins, GitLab CI, build automation, deployment pipeline.

DevOps Cloud•143L

Cloud Architecture

Design scalable, resilient, and cost-effective systems on cloud platforms like AWS, GCP, and Azure. Trigger keywords: cloud architecture, AWS, GCP, Azure, well-architected, multi-region, high availability, cloud-native.

DevOps Cloud•72L