Be honest about how your last AWS project's infrastructure started. You copied the Terraform from the previous repo, deleted the bits that threw errors, and moved on. Six months later nobody remembers why half of it is shaped the way it is, and there's a 500-line main.tf that everyone is scared to touch.
I got tired of that ritual, so I built a Terraform Blueprint Generator: pick your AWS stack, and it emits clean, production-structured Terraform in seconds.
What "production-structured" actually means
Not one giant file. Not resources with wide-open security groups because that was fastest. What you get:
- A sane module layout — separated concerns, not everything crammed into a single file.
- Secure defaults — least-privilege leanings, private-by-default networking, encryption where it belongs. The safe choice is the default choice, so you have to opt out of security rather than remember to opt in.
- Portable by design — no gratuitous single-vendor lock-in baked into the baseline. (That's the same posture behind our Vendor Lock-In Auditor — portability as a default, not an afterthought.)
What it is and isn't
It's a baseline you adapt, not a turnkey production deploy. You still:
- review every line (it's your infra, own it),
- set your own
tfvars, - decide and configure your state backend.
What it saves is the boring, error-prone bootstrapping — the part where inconsistency and quiet insecurity creep in. You start from a clean, well-organised foundation instead of last quarter's technical debt.
Free, no signup: framz.io/tools/terraform-blueprint-generator.
Why we made it
We build and run cloud infrastructure at Framz, and a consistent, portable, secure-by-default starting point is something we wanted for ourselves. So it's public and free.
Two questions for the DevOps crowd: which AWS stacks / resources should it cover next? And — the one that always starts a good argument — modules or a flat structure for a small team's baseline? Let me hear it in the comments.
SOCIAL SHARE CARD GENERATOR