Terraform Resource Generator

HCL (HashiCorp Configuration Language) is the configuration syntax used by Terraform. It describes infrastructure as code — declaring what resources you want (VMs, databases, buckets) and Terraform handles creating, updating, and destroying them to match that desired state.

This generator supports AWS (EC2, S3, RDS, Security Groups), GCP (Compute Engine, Cloud Storage), and Azure (Virtual Machines, Storage Accounts). Each provider has its own Terraform provider plugin you must configure separately.

Copy the output into a .tf file in your Terraform project directory. Run 'terraform init' to download the required provider plugins, 'terraform plan' to preview changes, then 'terraform apply' to create the resources. Always review the plan before applying.

The resource name (the string after the resource type) is a local identifier used within your Terraform configuration. It's not the same as the actual resource name in the cloud. For example, resource "aws_instance" "main" creates an EC2 instance referenced as aws_instance.main in HCL.

No — never commit terraform.tfstate to version control. It may contain sensitive data. Use a remote backend (S3, Terraform Cloud, GCS) to store state securely and enable team collaboration. Add *.tfstate and *.tfstate.backup to .gitignore.

Variables (var.*) let you parameterize configurations. Sensitive values like passwords should always be passed as variables rather than hardcoded in HCL. Use a terraform.tfvars file or environment variables (TF_VAR_name) to supply values.