Cloud · AWS
Reproducible AWS infrastructure: infrastructure as code with Terraform/OpenTofu
Your infrastructure as versioned code that is reviewable and easy to recreate, instead of settings clicked together in the console.
When infrastructure is built by hand, nobody knows for sure what is deployed, every environment is slightly different and recovering from a mistake is slow. I define your AWS infrastructure as code with Terraform or OpenTofu: every change goes through a reviewed plan before it is applied, environments stay consistent and everything is documented in the repository.
- AWS
- Terraform
- OpenTofu
- Infrastructure as code
Gallery
Packages
Three levels of scope. Pricing is quoted for your case.
Basic
A simple stack in code, or your most important existing resources brought under code.
Deliverables
- Terraform/OpenTofu code for the agreed resources
- Remote state with locking
- Usage documentation in the README
- Estimated delivery: 5 days
- 1 revision
Standard
The full infrastructure of one application, with staging and production environments.
Deliverables
- Everything in Basic
- Network, compute (Lambda or ECS Fargate) and data (RDS or DynamoDB)
- Least-privilege IAM permissions
- Staging and production environments from the same modules
- Estimated delivery: 10 days
- 2 revisions
Premium
Multi-environment infrastructure managed from CI, including importing what already exists.
Deliverables
- Everything in Standard
- Reusable modules
- A plan on every pull request and apply from GitHub Actions
- Import of hand-made resources
- Drift detection
- A handover session with your team
- Estimated delivery: 20 days
- 3 revisions
What I need from you
- Access to your AWS account through an IAM role or user for the project
- A description of the current architecture and resources
- The environments you need
- Your preferences or constraints on region, cost and compliance
Frequently asked questions
Terraform or OpenTofu?
They are compatible in most cases; OpenTofu is the open-source alternative. I recommend one based on your context and licensing.
Can you work with infrastructure that already exists?
Yes. Existing resources are imported into code without recreating them.
Will my production services be affected?
Every change is reviewed as a plan before it is applied, and risky changes are agreed with you and scheduled.
Who pays the AWS costs?
The infrastructure lives in your AWS account. I flag decisions that affect cost before making them.