Infrastructure as Code

The problem

Infrastructure changed by hand in a cloud console is infrastructure nobody can safely reproduce, review, or roll back. It works right up until the one person who remembers how it was configured is unavailable and something needs to change under pressure.

"We'll write the Terraform later" almost never happens — every manually-created resource is a small, compounding source of configuration drift between what's documented and what's actually running.

TekMage's approach

Every piece of infrastructure TekMage touches is defined in Terraform from the start, checked into version control, and applied through a reviewable plan/apply cycle — the same standard used across TekMage's own production sites, all three of which share a single Terraform-managed load balancer and DNS configuration.

That includes the boring-but-critical parts: state locking, environment separation, and treating a `terraform plan` that shows unexpected changes as a signal to stop, not a prompt to `-auto-approve` through it.