Generating Infrastructure as Code
Overview
Generate production-ready infrastructure as code for Terraform, CloudFormation, Pulumi, ARM templates, and AWS CDK. Produce modular, well-structured configurations with proper variable definitions, outputs, remote state management, and deployment guidance for AWS, GCP, and Azure cloud stacks.
Prerequisites
- Target cloud provider CLI installed and authenticated (
aws, gcloud, az)
- IaC tool installed: Terraform 1.0+, Pulumi 3+, AWS CDK, or relevant SDK
- Cloud credentials configured with permissions to create the target resources
- Understanding of the desired infrastructure architecture (compute, networking, storage, database)
- Version control repository for storing IaC configurations
Instructions
- Identify the IaC tool and cloud provider based on the project requirements and existing codebase
- Scan the project for existing IaC files to understand current patterns and conventions
- Define the modular file structure: separate files for providers, networking, compute, storage, and databases
- Generate the provider configuration with version pinning and remote backend for state storage
- Define input variables with types, descriptions, defaults, and validation rules for all configurable values
- Write resource definitions following cloud provider best practices: encryption enabled, logging configured, least-privilege IAM
- Add outputs for resource identifiers, endpoints, and connection strings needed by other modules or applications
- Configure remote state backend: S3 + DynamoDB for Terraform, Pulumi Cloud, or CloudFormation stack exports
- Create environment-specific variable files (
terraform.tfvars, dev.tfvars, prod.tfvars) for multi-environment deployment
- Validate with
terraform validate, terraform plan, or equivalent tool-specific linting
Output
- IaC configuration files organized by resource type or module
- Variable definition files with documented inputs and sensible defaults
- Output definitions for cross-module references and application configuration
- Backend configuration for remote state storage
- Environment-specific variable files for dev, staging, and production
- Deployment instructions with prerequisite setup and apply commands
Error Handling
| Error |
Cause |
Solution |
Invalid HCL syntax |
Malformed Terraform configuration |
Run terraform validate to identify the error; check bracket matching and attribute syntax |
Unable to authenticate with cloud provider |
Missing or expired credentials |
Run aws configure, gcloud auth login, or az login to refresh credentials |
Resource already exists |
Trying to create a resource that exists outside of IaC management |
Use terraform import to bring the existing resource under management |
Error acquiring state lock |
Another process holding the state lock |
Wait for the other process to finish; use terraform force-unlock <ID> if the lock is stale |
Dependency cycle detected |
Resources referencing each other circularly |
Refactor to remove the cycle; use data sources or depends_on to establish explicit ordering |
Examples
- "Generate Terraform for a production VPC on AWS with public/private subnets across 3 AZs, NAT gateways, VPC flow logs, and an EKS cluster."
- "Create a CloudFormation template for an S3 bucket with versioning, server-side encryption (KMS), public access block, and lifecycle rules."
- "Write Pulumi TypeScript code for a GCP Cloud Run service with a custom domain, Cloud SQL database, and Secret Manager integration."
Resources
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: jeremylongshore-claude-code-plugins-plus-skills-generating-i3description: Generating Infrastructure as Code4---5# Generating Infrastructure as Code67## Overview89Generate production-ready infrastructure as code for Terraform, CloudFormation, Pulumi, ARM templates, and AWS CDK. Produce modular, well-structured configurations with proper variable definitions, outputs, remote state management, and deployment guidance for AWS, GCP, and Azure cloud stacks.1011## Prerequisites1213- Target cloud provider CLI installed and authenticated (`aws`, `gcloud`, `az`)14- IaC tool installed: Terraform 1.0+, Pulumi 3+, AWS CDK, or relevant SDK15- Cloud credentials configured with permissions to create the target resources16- Understanding of the desired infrastructure architecture (compute, networking, storage, database)17- Version control repository for storing IaC configurations1819## Instructions20211. Identify the IaC tool and cloud provider based on the project requirements and existing codebase222. Scan the project for existing IaC files to understand current patterns and conventions233. Define the modular file structure: separate files for providers, networking, compute, storage, and databases244. Generate the provider configuration with version pinning and remote backend for state storage255. Define input variables with types, descriptions, defaults, and validation rules for all configurable values266. Write resource definitions following cloud provider best practices: encryption enabled, logging configured, least-privilege IAM277. Add outputs for resource identifiers, endpoints, and connection strings needed by other modules or applications288. Configure remote state backend: S3 + DynamoDB for Terraform, Pulumi Cloud, or CloudFormation stack exports299. Create environment-specific variable files (`terraform.tfvars`, `dev.tfvars`, `prod.tfvars`) for multi-environment deployment3010. Validate with `terraform validate`, `terraform plan`, or equivalent tool-specific linting3132## Output3334- IaC configuration files organized by resource type or module35- Variable definition files with documented inputs and sensible defaults36- Output definitions for cross-module references and application configuration37- Backend configuration for remote state storage38- Environment-specific variable files for dev, staging, and production39- Deployment instructions with prerequisite setup and apply commands4041## Error Handling4243| Error | Cause | Solution |44|-------|-------|---------|45| `Invalid HCL syntax` | Malformed Terraform configuration | Run `terraform validate` to identify the error; check bracket matching and attribute syntax |46| `Unable to authenticate with cloud provider` | Missing or expired credentials | Run `aws configure`, `gcloud auth login`, or `az login` to refresh credentials |47| `Resource already exists` | Trying to create a resource that exists outside of IaC management | Use `terraform import` to bring the existing resource under management |48| `Error acquiring state lock` | Another process holding the state lock | Wait for the other process to finish; use `terraform force-unlock <ID>` if the lock is stale |49| `Dependency cycle detected` | Resources referencing each other circularly | Refactor to remove the cycle; use data sources or `depends_on` to establish explicit ordering |5051## Examples5253- "Generate Terraform for a production VPC on AWS with public/private subnets across 3 AZs, NAT gateways, VPC flow logs, and an EKS cluster."54- "Create a CloudFormation template for an S3 bucket with versioning, server-side encryption (KMS), public access block, and lifecycle rules."55- "Write Pulumi TypeScript code for a GCP Cloud Run service with a custom domain, Cloud SQL database, and Secret Manager integration."5657## Resources5859- Terraform documentation: https://developer.hashicorp.com/terraform/docs60- AWS CloudFormation: https://docs.aws.amazon.com/cloudformation/61- Pulumi: https://www.pulumi.com/docs/62- AWS CDK: https://docs.aws.amazon.com/cdk/v2/guide/63- Azure ARM/Bicep: https://learn.microsoft.com/en-us/azure/azure-resource-manager/6465---66> Converted and distributed by [TomeVault](https://tomevault.io/claim/jeremylongshore) — claim your Tome and manage your conversions.67<!-- tomevault:4.0:skill_md:2026-04-11 -->
tomevault-io