Infrastructure as Code
Your infrastructure, written down, reviewable and reproducible.
Infrastructure that only exists in a console cannot be reviewed, cannot be rebuilt and cannot be handed over. We describe it in code, keep it in your repository, and make a new environment something you create deliberately rather than something you configure by hand over two careful days.
Tools we work in
- Terraform
- OpenTofu
- AWS
- Azure
- Google Cloud
- GitHub Actions
- Docker
Scope
What this covers
The specific work included when you engage us for this service.
- Import of the existing estate into code without tearing it down first
- Environment definitions for development, staging and production from one source
- Peer review and a plan output before anything is applied
- Remote state, locking and clean separation between environments
- Reusable modules for the patterns you repeat, versioned and documented
- Drift detection so manual changes become visible instead of silent
What you receive
- 01The estate described in code, committed to your repository and applied through the pipeline
- 02A module structure your team can extend, with variables documented
- 03A migration note explaining how anything imported by hand was brought under management
Questions
Infrastructure as Code, answered
Do we have to rebuild everything from scratch?
No, and doing so would be reckless. Existing resources are imported into the code one at a time, with the plan output reviewed at each step so nothing is destroyed. It is slower to start than a greenfield build and considerably less exciting, which is the point when real customers are using the system.
Which tool should we use?
Terraform or OpenTofu for almost everything, because the provider ecosystem is the broadest and hiring is easiest. Pulumi and CDK are strong options if your team already writes TypeScript or Python fluently, since they remove a second language from the stack. The wrong choice is maintaining three tools, so we consolidate rather than add.
What stops someone making a change in the console?
Nothing stops it technically, and that is fine. What matters is that the change is detected as drift on the next plan and either codified or reverted deliberately. We also reduce permissions for destructive console actions where the team is comfortable, but the real fix is the detection, not the barrier.
Most often requested by
Related
More in Cloud, DevOps & Security
Cloud Migration
Move to the cloud without carrying the old problems with you.
Cloud Architecture & Design
Decisions that are cheap now and expensive to reverse later.
Cloud Cost Optimisation
Most cloud bills contain spend that nobody decided to make.
CI/CD & Release Engineering
Deploys that are boring, which is exactly the point.
Tell us where the manual work is
A 30-minute call. We map the process, tell you what we would automate or build first, and what it costs. No retainer before you agree the scope.
- No retainer before scope is agreed
- Written plan you can act on alone
- Worldwide delivery, on your hours