From ClickOps to Terraform: what we measured

How we cut MTTR and why state files deserve respect.

Sahil BansalConnect

1 min readFeb 1, 2026

Infrastructure as code

Problem

Manual cloud changes (ClickOps) caused drift, weak audit trails, and hard-to-reproduce incident fixes.

Solution

We moved core AWS resources to Terraform modules, standardized environments, and enforced PR-based infra changes.

Impact

MTTR dropped, rollbacks became predictable, and infra changes became reviewable and repeatable.

Terraform
AWS
MTTR

Infrastructure as code

Written by Sahil Bansal

DevOps and platform engineer. I write about the infrastructure decisions I have had to live with.

More from Sahil Bansal

Infrastructure as code

You Don’t Need DynamoDB for Terraform State Locking Anymore

Terraform 1.10+ can lock state natively in S3, so the DynamoDB table is optional. When to migrate, and the trade-offs.

May 14, 20263 min readMedium

Infrastructure as code

Terragrunt Is Not a Silver Bullet: The Real Operational Trade-offs of Scaling Terraform Across Environments

Terragrunt ends copy-pasted environments and drift, but adds a layer of its own to operate. Where it pays off and when to skip it.

Jun 9, 20265 min readMedium

Security

The frontend is not a security boundary

Notes on AWS Builder Center’s frontend security article: enforcement belongs behind the frontend, not in it.

Aug 21, 20261 min readFrom LinkedIn

Security

Your pipeline has more access than any engineer on your team

A 60-second check of your GitHub Actions workflows for the patterns CI supply-chain attacks rely on: pull_request_target, movable tags, long-lived keys and default token permissions.

Oct 8, 20262 min readFrom LinkedIn

See all from Sahil Bansal