Infrastructure as Code (Terraform)
Everything your cloud runs, defined in Terraform: reviewable, repeatable, and safe to change.
Automate
Click-ops does not scale and cannot be reviewed. I codify your infrastructure in Terraform with remote state, a module layout that stays readable, and a plan/apply workflow that shows exactly what will change before it does.
- Terraform codebase with remote state + locking (S3+DynamoDB or GCS)
- Module layout separating reusable building blocks from per-environment config
- Import of existing resources so state matches reality — no big-bang recreate
- Multi-environment pattern (develop / staging / production) from one codebase
- CI pipeline: fmt, validate, tflint, plan on MR, gated apply on merge
- A runbook: how to add a resource, promote a change, and recover state
One codebase, many environments
The same modules build every environment. What differs — sizes, counts, domains — lives in a per-environment variables file. No copy-pasted directories drifting apart, no 'it works in staging' surprises.
Changes you can see before they happen
Every merge request runs terraform plan and posts the diff. Nothing applies until a human approves the merge. Production applies are a manual gate on top of that.
Adopting messy existing infra
If resources already exist, I import them into state rather than destroying and recreating. The end state is code that matches what is actually running, reached without an outage.
FAQ
Have a project in mind?
Tell me what you are building. You get a scoping call and a fixed quote — no obligation.