Terragrunt - make your Terraform code DRY

Learn how to keep your Terraform and Terragrunt code dry by using modules to reuse components, centralizing remote state configuration, extracting common environment settings, and standardizing command line flags.

Keep your Terraform CLI configuration DRY with Terragrunt by centralizing extra arguments, environment variables, required and optional var files, and organizing the setup for clarity.

Terragrunt hooks enable before, after, and error actions triggered around plan, apply, and destroy; define unique hook names and attach custom scripts to run, log, or notify during Terraform operations.

Apply the fmt command to automatically format Terragrunt code recursively from the root directory, align lines, and keep changes in place, enabling clean code and CI/CD integration.

Discover how to run all Terragrunt modules in a single batch to manage entire environments, speed up plan and apply, and observe dependency flows across database, application, and load balancer.

Keep your Terragrunt architecture dry by extracting common module configuration into a directory, then include it from dev and prod environments, focusing on Terraform source and inputs to reduce duplication.

Demonstrate before, after, and error hooks in Terragrunt, applied to init, plan, and apply, including simple echo notifications and error handling options.

Understand how AWS costs can accumulate, learn about the free tier and always free resources, and follow best practices to shut down instances and remove unused resources.

Learn to keep dependencies dry by using Terraform's dependency blocks to pass module outputs (security group IDs, bucket names) between modules, making configs dynamic and reducing manual input.