Why Terraform is green when your cloud is broken

The article discusses the challenges and solutions related to infrastructure drift in cloud environments when using Infrastructure as Code (IaC) tools like Terraform. Here are the key points:

Challenges of Drift

1. Terraform State File Limitations: The state file maintained by Terraform only reflects what it thinks is running, not necessarily what's actually deployed in your cloud environment.
2. Manual Changes and Scale Issues:
   • As environments scale (multiple accounts, regions), manually tracking drift becomes impractical.
   • Manual audits and console checks are time-consuming and error-prone.

Solutions

1. CloudQuery: A tool that syncs actual cloud state into SQL tables, allowing you to query your infrastructure as if it were a database:

   • Example Query: SELECT account_id, region, instance_id, tags FROM aws_ec2_instances WHERE tags->>'owner' IS NULL ORDER BY account_id, region;
   • This helps identify discrepancies between what's actually running and what Terraform thinks is running.

2. Identifying Drift:

   • If a resource exists in the cloud but not in your IaC state: Use terraform import to bring it under management.

Read the full article at The New Stack

---

Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.