Terraform Engineer
Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP.
Before & after
Same prompt, same agent — the only difference is the skill.
Setting up AWS infrastructure with Terraform is definitely achievable. That's a good approach because it's infrastructure-as-code and repeatable. To build the right setup, I need to understand your requirements. What does your web app do, and what's the expected scale — are we talking hundreds of daily users or millions? Do you need high availability across multiple regions, or is a single region okay? For compute, are you thinking EC2 instances, containers on ECS, or serverless with Lambda? Do you need a database — managed RDS or self-hosted? What about storage — S3 for static assets? And networking — do you need a load balancer, VPN, or any special security requirements? Also, do you have existing AWS infrastructure, or is this brand new? What's your DevOps experience level — are you looking for a production-ready setup or something to learn with? Once I know these details, I can design a Terraform architecture that fits your needs.
AWS TERRAFORM ARCHITECTURE - MULTI-ENVIRONMENT SETUP
STACK OVERVIEW
Region: us-east-1 (primary) + us-west-2 (DR)
Environments: dev, staging, prod
Compute: ECS on Fargate (containerized) + ALB
Database: RDS PostgreSQL 15 (Multi-AZ for prod)
Storage: S3 for assets + CloudFront CDN
Secrets: AWS Secrets Manager
TERRAFORM STRUCTURE
├── main.tf (provider, backend)
├── vpc.tf (networking, subnets, security groups)
├── ecs.tf (task definitions, services)
├── rds.tf (database, parameter groups)
├── s3.tf (buckets, lifecycle policies)
├── alb.tf (load balancer, listeners, target groups)
├── variables.tf (env vars, instance counts)
├── terraform.tfvars (per-environment config)
├── outputs.tf (load balancer URL, DB endpoint)
└── modules/
├── networking/
├── database/
└── compute/
KEY MODULES
Module: networking
• VPC (10.0.0.0/16)
• Public subnets (3 AZs, /24 each)
• Private subnets (3 AZs, /24 each)
• NAT gateways for outbound from private
• Security groups (ALB, ECS, RDS)
Module: database
• RDS instance (db.t3.medium)
• Multi-AZ enabled (prod only)
• Backup retention: 30 days
• Parameter group (custom settings)
• Secrets Manager for password rotation
Module: compute
• ECS cluster (3 instances)
• Task definition (2 CPU, 4GB memory)
• Auto-scaling group (min 3, max 10 tasks)
• Container image from ECR
DEPLOYMENT STEPS
1. terraform init (backend: S3 + DynamoDB state lock)
2. terraform plan -var-file=environments/prod.tfvars
3. Review output (resources, counts, changes)
4. terraform apply -auto-approve
5. Run smoke tests against ALB endpoint
6. Configure DNS (Route53 or external)
COST ESTIMATE (prod, monthly)
ALB: $16 + $0.006/hour traffic = $50
ECS Fargate: 3 tasks * 2 CPU * $0.0441/h = $950
RDS: db.t3.medium Multi-AZ = $300
S3 + CloudFront: $50-100
Total: ~$1350/month
SECURITY
• Security groups: whitelist only needed ports
• RDS: encrypted at rest (AWS KMS)
• Secrets: auto-rotate every 30 days
• Terraform state: encrypted S3 backend
• IAM: least-privilege roles for servicesAbout this skill
name: terraform-engineer description: Use when Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP.
Terraform Engineer
Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.
What you get
- Public GitHub repo
- the skills/terraform-engineer folder with SKILL.md and references.
Customize your output
- Fork the repo and extend the skill's reference files for your own stack conventions.
Example output
Activates on a matching request (e.g. building or reviewing Terraform Engineer code) and can chain with other skills in the pack.
Best for
Full-stack developers and engineering teams using Claude Code.
SKILL.md preview
---
name: terraform-engineer
description: Use this skill when implementing infrastructure as code with Terraform across AWS, Azure, or GCP.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Terraform Engineer
Builds and maintains Terraform infrastructure as code — reusable modules, safe state management, and multi-environment workflows — across AWS, Azure, and GCP.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.