Infrastructure as Code with Terraform and Federico Calo's Tools

Generate Terraform HCL files (main.tf, variables.tf, outputs.tf, provider.tf) for AWS, Azure, and GCP via visual form. Zero configuration, all in the browser.

Cloud Provider

Usato per var.region e per il provider block.

Aggiungi Risorsa

Nessuna risorsa aggiunta

Seleziona un tipo di risorsa e clicca "Aggiungi" per cominciare a costruire la tua infrastruttura Terraform.

main.tf
# No resources added yet.
# Use the form to add resources and generate your Terraform configuration.
Tutti i file in un unico testo concatenato

Come usarlo

  1. Seleziona il cloud provider (AWS, Azure, GCP)
  2. Imposta la regione di deploy
  3. Aggiungi le risorse e configura i campi
  4. Copia o scarica i file generati
  5. Esegui terraform init && terraform plan

Nota sui valori sensibili

Password e chiavi SSH sono definiti come sensitive = true nelle variabili. Usare sempre un backend remoto (S3, Azure Blob, GCS) per lo state file e un secret manager per i valori sensibili.

Struttura consigliata

📁terraform/
📄provider.tf
📄main.tf
📄variables.tf
📄outputs.tf
📄terraform.tfvars

Come utilizzare Terraform Generator

Choose a Cloud Provider

Choose AWS, Azure or GCP: The list of available resources and default region are automatically updated.

Set Region

Verify or modify the region/location used for the provider block and variable var.region.

Add Resources

Choose a resource type (VPC, EC2, RDS, S3, VM, SQL...) from the menu, click "Add Resource" and fill in each field's specifics.

Copy or download generated files

Pass through main.tf, variables.tf, outputs.tf and provider.tf, then copy or download the single file or entire concatenated Terraform project.

Suggerimenti

  • Run terraform init and terraform plan before applying to verify expected changes.
  • Don't commit sensitive values to a Terraform.tfvars file outside of .gitignore, never commit them to the repository.
  • Organize downloaded files in the recommended structure (provider.tf, main.tf, variables.tf, outputs.tf) to keep the project readable.

Domande frequenti

Is the generated code ready for production use?

The tool generates a syntactically correct and coherent HCL base that follows best practices (tags, sensitive variables, output), but should always be reviewed, adapted to your context, and tested with Terraform Plan before applying it in production.

Where are sensitive values such as passwords and SSH keys managed?

Password and SSH keys are defined as sensitive variables with `true` in `variables.tf`: the actual value is provided at runtime (e.g., via `terraform.tfvars`, excluding from Git or a secret manager), never hardcoded in generated code.

Do you have an active cloud account to use the generator?

No. File generation in .tf happens entirely in the browser: no request to AWS, Azure or GCP is made until you run Terraform init/apply with your actual credentials.

What Terraform and provider versions are being used?

Block Terraform requires version >= 1.6.0 and uses official HashiCorp providers (hashicorp/aws > 5.0, hashicorp/azurerm > 3.80, hashicorp/google > 5.0): you can still modify the version constraints in the generated provider.tf file.

Where are saved the Terraform state files?

Don't create a backend configuration for this state - it's recommended to manually configure a remote backend (S3, Azure Blob Storage or GCS) instead of using the local state, especially for team projects.

All Tools