Generate realistic Terraform plan and apply logs with AWS, Azure, and GCP resources. Simulate state management and infrastructure changes for IaC training and demos.
Press Ctrl + C to exit. Output is simulated for demo purposes only.
This module simulates resource apply, state lock, and provider actions log events with realistic pacing.
It is designed for demos, log pipeline testing, and documentation where the real stack is unavailable.
All output is generated locally in the browser and is safe to run.
Acquiring state lock. This may take a few moments... aws_instance.web: Creating... aws_instance.web: Creation complete after 12s [id=i-0abc1234] aws_security_group.web: Modifying... [id=sg-1234abcd] Apply complete! Resources: 3 added, 1 changed, 0 destroyed.
No. It is a simulator that prints log text only.
Yes. The CLI supports speed and repeat options, and the web page can be refreshed.
No. It does not install, update, or modify anything.
Terraform plan and apply produce resource creation, modification, and state lock messages. DevOps teams use these logs in CI and audits.
This simulator generates similar output so you can test log pipelines or demo infrastructure-as-code without running Terraform.
Popular questions and answers from Stack Overflow related to Terraform.
terraform plan shows what changes will be made without executing them - it is a dry run. terraform apply actually creates/modifies/destroys resources. Always run plan before apply to review changes.
State lock prevents concurrent modifications. If stuck, use terraform force-unlock LOCK_ID. Check if another process is running. For remote state, verify backend connectivity and permissions.
Use terraform import resource_type.name resource_id. Example: terraform import aws_instance.web i-1234567890. Then write matching config. Use terraform state show to see attributes.
State maps config to real resources, tracks metadata, and improves performance. Without state, Terraform cannot know what exists. Use remote state (S3, GCS) for teams. Never edit state manually.
Declare with variable block, reference with var.name. Set via -var flag, terraform.tfvars, environment (TF_VAR_name). Use locals for computed values. Variables can have defaults and validation.
count creates numbered instances (count.index). for_each creates named instances with keys. for_each is preferred - avoids index shift issues when removing items from middle of list.
Options: workspaces (terraform workspace new prod), separate directories per env, or use tools like Terragrunt. Workspaces share code with different state. Directories offer more isolation.
Use terraform destroy -target=resource_type.name. Or remove from config and apply. Be careful with dependencies. -target is for exceptional cases, not regular workflow.
Modules are reusable groups of resources. Use for: repeated patterns, team sharing, organization. Call with module block. Modules have inputs (variables) and outputs. Version modules for stability.
Never commit secrets to git. Options: environment variables, AWS Secrets Manager/HashiCorp Vault data sources, encrypted tfvars (git-crypt), CI/CD secret injection. Mark sensitive variables.
Popular video tutorials to learn more about Terraform.
TechWorld with Nana
Complete Terraform course covering HCL syntax, providers, state management, modules, and infrastructure as code best practices.
Watch on YouTubefreeCodeCamp.org
Build AWS infrastructure with Terraform including VPCs, EC2, RDS, and implementing production-ready architectures.
Watch on YouTube
