Dev
Generador de prompts de recurso de Terraform
Used by developers, writers, and creators worldwide.
A Terraform resource prompt generator builds a tight, fill-in request you can give an AI assistant so it returns infrastructure code that follows good practice instead of a bare minimal block. Choose your cloud provider and describe the resource you want, and it produces a prompt that asks for a pinned provider version, variables instead of hardcoded values, standard tags, secure defaults, the companion resources that usually travel together, and an output for the id or ARN. Platform engineers use it to get consistent, review-ready HCL, to avoid the missing-encryption and public-access mistakes that slip into quick examples, and to standardise how their team requests infrastructure. It runs in your browser and generates instantly. Edit the resource description to match what you are provisioning, then paste the prompt into your assistant. The explicit requirements steer the model toward code you can actually merge.
Read the complete guide — 5 min read
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Pick your cloud provider.
- Describe the resource you want to provision.
- Click Generate to build the prompt.
- Paste it into your AI assistant and run terraform plan on the result.
Use Cases
- •Getting review-ready Terraform HCL from an AI assistant
- •Avoiding insecure defaults in quickly generated infrastructure
- •Standardising how a team requests cloud resources
- •Scaffolding a module with variables, tags, and outputs
- •Provisioning across AWS, Azure, or Google Cloud consistently
Tips
- →Name the exact resource type if you know it, like aws_s3_bucket.
- →Ask for encryption and versioning explicitly for storage resources.
- →Request outputs so the resource plugs into other modules.
- →Always review and plan before applying generated HCL.
FAQ
why ask for variables and tags
Hardcoded names and untagged resources are the two most common problems in generated Terraform. Asking for variables keeps the code reusable across environments, and standard tags let teams track cost and ownership from day one.
does it lock me to one provider
No. You choose AWS, Azure, or Google Cloud, and the prompt adapts the provider line. The requirements — pinned versions, secure defaults, outputs — apply equally across providers, so the structure is portable.
will the output be safe to apply
The prompt steers the assistant toward secure defaults and no hardcoded secrets, but always run terraform plan and review the result before applying. Treat generated infrastructure code with the same scrutiny as any pull request.
You might also like
Popular tools from other categories that share themes with this one.