Generate Terraform Infrastructure from Plain-English Requirements
Terraform is powerful but verbose — even simple infrastructure requires a lot of boilerplate. Describe what you need and Claude will write idiomatic HCL with sensible defaults.
Write Terraform for an AWS setup with:
- A VPC with two public and two private subnets across two availability zones
- An RDS PostgreSQL 16 instance in the private subnets (db.t3.medium)
- An EC2 Auto Scaling group behind an Application Load Balancer
- Security groups that allow HTTPS in, and the app to reach the database
- All credentials in variables with no hardcoded values
Claude will produce properly structured Terraform with a variables.tf, outputs.tf, and logical resource grouping. Specify your provider and region and it'll include the correct provider block too.
You can ask it to go further:
Add an S3 bucket for file storage with versioning enabled, a CloudFront
distribution in front of it, and an IAM role the app can assume to write to it.
Claude also helps when you're stuck on the Terraform way of doing something familiar:
I want to run a database migration command after my EC2 instance launches.
What's the correct Terraform pattern for this — user data, null_resource, or
something else?
Terraform is mostly typing. Let Claude do the typing.
Log in to leave a comment.
The /security-review command scans your uncommitted changes for injection vectors, auth gaps, hardcoded secrets, and other common vulnerabilities.
The SessionStart hook fires when any session begins or resumes, making it ideal for loading environment variables and running one-time setup scripts.
Ask Claude to write property-based tests for your functions using fast-check — it identifies the mathematical invariants in your code and generates tests that cover inputs you'd never enumerate by hand.