
Terraform and Infrastructure as Code: your cloud described in a repository
We describe your infrastructure in Terraform: networks, servers, clusters, databases, DNS, access. What was created by hand is imported into code without being recreated. After that every change is a pull request with a plan you can read before it is applied.
When you need this
- 1
Resources were created in the console and nobody remembers why
- 2
A second environment is needed and the first one cannot be reproduced
- 3
Terraform exists, but the state is local or the plan shows unexpected changes
- 4
One person runs apply from a laptop and the rest wait
- 5
You open new projects or regions and copy the configuration by hand
What's included
Inventory and import
We list what exists in the account (on AWS usually the VPC, EC2, RDS, S3, IAM and EKS) and import it into Terraform state. Resources are not recreated; the goal is a plan that shows no changes.
Modules
Repeated parts, such as a network, a cluster, a database or a service, become modules with clear inputs and outputs and pinned versions.
State and environments
Remote state with locking and encryption, a separate state per environment. Terragrunt is added where there are many environments or accounts and the configuration should not be copied.
Plan on pull request
CI runs fmt, validate and plan on every pull request and posts the plan as a comment. Apply runs after merge, from the pipeline, not from a laptop.
Access and secrets
The pipeline gets its own role with limited permissions, through OIDC where the cloud supports it, so no long-lived keys sit in CI. Secrets stay out of the code: encrypted with SOPS or kept in the cloud's secret store.
Templates and documentation
Your team gets templates for a new service or environment and a short guide: how to add a resource, how to read a plan, what to do when the state drifts.
How the work goes
- 1
Call and access
You show what runs and where. We get read access to the cloud account and to the existing code, if there is any.
- 2
Plan and price
Which resources go into code first, how state and environments are laid out, what the pipeline looks like. Scope and price are agreed before work starts.
- 3
Import and write
We import resources group by group and open pull requests. Each one ends with a plan that shows no changes to the live infrastructure.
- 4
Pipeline and handover
Plan and apply move into CI. We walk your team through the repository, or keep maintaining it under a support agreement.
Questions
- Terraform
- Terragrunt
- AWS
- Hetzner
- Cloudflare
- Kubernetes
- Helm
- GitHub Actions
- GitLab CI
- SOPS
Describe the task — get a plan and a price
Write what you have and what you need. We answer within one business day with questions or a concrete proposal.