Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/detecting-infrastructure-drift

@820dfc8
Run it yourself

Execute use when detecting infrastructure drift from desired state. Trigger with phrases like "check for drift", "infrastructure drift detection", "compare actual vs desired state", or "detect configuration changes". Identifies discrepancies between current infrastructure and IaC definitions using terraform plan, cloudformation drift detection, or manual comparison.

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/detecting-infrastructure-drift

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈100 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈433 more on demand in 3 files.

Description uses 5.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈401 characters, or 5.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Detecting Infrastructure Drift

Current State

!ls *.tf Dockerfile docker-compose.yml 2>/dev/null || echo 'No IaC files found' !terraform version 2>/dev/null || echo 'Terraform not installed'

Overview

Detect discrepancies between actual cloud infrastructure state and the desired state defined in IaC (Terraform, CloudFormation, Pulumi). Run drift detection commands, analyze modified/added/deleted resources, generate drift reports with affected resources, and provide remediation steps to bring infrastructure back into compliance.

Prerequisites

  • IaC configuration files up to date in the project directory
  • Cloud provider CLI installed and authenticated with read access to all managed resources
  • IaC tool installed: Terraform 1.0+, AWS CLI (for CloudFormation drift), or Pulumi
  • Remote state storage accessible and current (S3 backend, Terraform Cloud, Pulumi Cloud)
  • Read-only IAM permissions for all resource types managed by IaC

Instructions

  1. Identify the IaC tool in use by scanning for .tf files, template.yaml, or Pulumi.yaml
  2. Initialize the IaC tool if needed: terraform init to download providers and configure backend
  3. Run drift detection: terraform plan -detailed-exitcode (exit code 2 = drift detected), aws cloudformation detect-stack-drift, or pulumi preview
  4. Parse the output to identify resources with drift: added (exists in cloud but not in IaC), modified (attributes changed), or deleted (in IaC but missing from cloud)
  5. For each drifted resource, determine if the drift is intentional (manual hotfix) or unintentional (configuration error, unauthorized change)
  6. Generate a structured drift report with resource identifiers, attribute differences, and severity classification
  7. Provide remediation options per resource: terraform apply to enforce desired state, terraform import to adopt changes, or update IaC to match reality
  8. Schedule recurring drift detection: configure a cron job or CI pipeline to run daily and alert on drift
  9. Investigate the root cause: determine who made the manual change and implement guardrails (SCPs, IAM restrictions) to prevent recurrence

Output

  • Drift detection report with resource-level detail: resource type, ID, drifted attributes, expected vs. actual values
  • Remediation commands: terraform apply, terraform import, or IaC code updates
  • CI/CD pipeline step for automated drift detection on a schedule
  • Alert configuration for drift detection results (Slack, email, PagerDuty)
  • Prevention recommendations: IAM policy restrictions, SCP guardrails, automated enforcement

Error Handling

Error Cause Solution
Error acquiring state lock Another Terraform process is running or stale lock Wait for the other process; use terraform force-unlock <ID> if the lock is stale
Unable to authenticate to cloud provider Expired or missing credentials Refresh with aws configure, gcloud auth login, or az login
No state file found Backend not initialized or state file deleted Run terraform init to configure the backend; restore state from backup if deleted
Access denied reading resource IAM policy missing read permissions for some resource types Grant read-only access for all resource types managed by IaC (ReadOnlyAccess or specific policies)
State file version mismatch Terraform version newer than state format Upgrade Terraform to match the state version or use terraform state replace-provider

Examples

  • "Run drift detection against all Terraform-managed infrastructure and generate a report of resources that have changed since last apply."
  • "Set up a daily GitHub Actions workflow that runs terraform plan and posts drift results to Slack if any resources are out of sync."
  • "Detect CloudFormation stack drift for the production VPC stack and provide remediation steps for any MODIFIED resources."

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides tools and instructions for detecting infrastructure drift in cloud environments using Terraform, AWS CloudFormation, and Pulumi. It uses benign environment checks during loading and follows standard DevOps practices.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 3 months ago
What it can do
Reads files Edits files Runs commands
version
1.24.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "devops",
  "terraform",
  "detecting-infrastructure"
]
All 8 allowed tools
ReadWriteEditGrepGlobBash(terraform:*)Bash(aws:*)Bash(gcloud:*)
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/detecting-infrastructure-drift