Skip to content
~/Terraform Snippet Generator
$

Terraform Snippet Generator

Generate production-ready Terraform/HCL code for AWS, GCP, and Azure — pick a provider, choose a resource, configure options, and export ready-to-use .tf files.

Cloud Provider

Presets

Resource Type

EC2 Instance Configuration

aws_instance

Instance Name

AMI ID

Instance Type

Key Pair Name

Subnet ID (optional)

Security Group IDs (comma-separated)

Tags (key=value, comma-separated)

User Data (shell script)

Generated Terraform Code

terraform {
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 5.0"
}
}
}
 
provider "aws" {
region = var.aws_region
}
 
# ---------------------------------------------------------------------------
# Variables
# ---------------------------------------------------------------------------
 
variable "aws_region" {
description = "AWS region"
type = string
default = "us-east-1"
}
 
# ---------------------------------------------------------------------------
# Resources
# ---------------------------------------------------------------------------
 
resource "aws_instance" "main" {
ami = "ami-0c55b159cbfafe1f0"
instance_type = "t2.micro"
tags = {
Name = "main"
}
}
 
output "main_public_ip" {
description = "Public IP of the EC2 instance"
value = aws_instance.main.public_ip
}
 
output "main_instance_id" {
description = "Instance ID"
value = aws_instance.main.id
}

What is Terraform and HCL?

Terraform is an infrastructure-as-code tool that lets you declare cloud resources in HCL (HashiCorp Configuration Language) files instead of clicking through consoles. You describe the end state — an EC2 instance, a VPC, a storage bucket — and Terraform computes the API calls needed to get there. Because infrastructure lives in plain text, you can version it in git, review it in pull requests, and reproduce an entire environment from scratch.

How does this generator work?

Pick a provider — AWS, GCP, or Azure — then a resource type: EC2, S3, RDS, or VPC on AWS; Compute Engine, Cloud Storage, Cloud SQL, or VPC on GCP; Resource Group, VM, Storage Account, or App Service on Azure. Fill in the form fields and the tool emits complete HCL, including the provider block, variables, and useful outputs. Copy the code or download it as main.tf — everything is generated in your browser, no cloud credentials required or sent anywhere.

What do I do with the generated code?

Save the snippet as main.tf in an empty directory, then run terraform init to download the provider plugin, terraform fmt to normalize formatting, and terraform validate to catch syntax errors. terraform plan shows exactly what would be created without touching anything — always read the plan before terraform apply. Treat generated code as a reviewed starting point: adjust regions, instance sizes, and tags to match your environment before applying.

Should I commit terraform.tfstate to git?

No. The state file records every attribute of every managed resource — including database passwords, private IPs, and access keys — in plain JSON, so committing it leaks secrets to anyone with repo access. It also invites corruption when two people apply at once. Use a remote backend instead: an S3 bucket with DynamoDB locking, a GCS bucket, or Terraform Cloud. Add terraform.tfstate and .terraform/ to .gitignore on day one.

What are common Terraform errors for beginners?

Error acquiring the state lock usually means a crashed run left a stale lock — inspect and use terraform force-unlock only when you are sure no apply is running. A resource already exists error means it was created outside Terraform; bring it under management with terraform import rather than deleting it. Unpinned provider versions cause builds that worked yesterday to break today, so set required_providers with a version constraint. And drift from console edits shows up as surprise changes in the next plan.

Why use Terraform instead of the cloud console?

Console changes are invisible: nobody reviews them, nobody can reproduce them, and six months later nobody remembers why that security group rule exists. With Terraform every change is a diff a teammate can approve, and terraform plan acts as a dry run before anything is touched. It is also multi-cloud — the same workflow and language manage AWS, GCP, and Azure — unlike CloudFormation or ARM templates, which lock you to a single vendor.

Is the generated HCL production-ready?

It is valid, idiomatic HCL that passes terraform validate, but production hardening is on you. Review defaults before applying: prefer private S3 ACLs with encryption and versioning enabled, restrict security groups instead of allowing 0.0.0.0/0, enable Multi-AZ and sensible backup retention for databases, and never hardcode secrets — pass them as sensitive variables or pull them from a secrets manager. The generator includes tags fields; use them, because untagged resources are how surprise cloud bills happen.