FAQ

How does Terragrunt keep configuration DRY across environments?

Terragrunt allows shared configuration to be defined once and inherited across units. Common backend settings, provider configuration, module inputs, and environment conventions can be centralized so the same code is not repeated across development, staging, and production. This is especially useful when the same infrastructure pattern, such as a VPC, cluster, database, and application stack, must be deployed across multiple environments. You define the common configuration once and override only the values that differ by environment.

Supercharge

Terragrunt for your Organization

Unlock Terragrunt’s full potential with Terragrunt Scale — purpose-built tooling that streamlines deploying and operating your infrastructure.

Automate your CI/CD

Terragrunt Pipelines

is an out-of-the-box, best practices, secure CI/CD pipeline, built for Terragrunt, by the creators of Terragrunt.

Remediate infra drift

Terragrunt Drift Detection

regularly compares your live cloud resources to your IaC and automatically opens pull requests to eliminate infrastructure drift.

Keep your IaC Fresh

Terragrunt Patcher

is a dependency management tool that keeps your OpenTofu/Terraform modules up to date, even through breaking changes.

Learn about Terragrunt Scale
Check out our other open source tools
Terratest
Validate IaC modules
Boilerplate
Automate repetitive DevOps work
CloudNuke
Save money on unused AWS resources
GitXargs
Make changes across git repos