Catching Terraform Drift Early: Scheduled Plans in GitHub Actions with AWS OIDC

<p>Terraform assumes it's the only thing managing your infrastructure. The moment something changes outside of Terraform — a manual console edit, an auto-scaler adjusting

<h2> When Terraform Gets Slow </h2> <p>Our Terraform state file grew to 500+ resources. Plans took 8 minutes. Applies timed out. State locking conflicts were daily. Something had

<p><strong>Introduction</strong></p> <p>A <strong>two-tier architecture</strong> on AWS — the bread and butter of real-world cloud deployments. Here's the idea:</p> <ul> <li>