FAQ

How does Pipelines ensure least privilege access?

Access control to infrastructure is segmented by least privilege principals (e.g. AWS IAM roles) that only have access to individual environments, further segmented by a different principal used for read-only access during pull requests / merge requests open and a principal used for read-write access during pull request merge.

As a consequence, updates to a particular environment will only be done by a principal that only has access to that environment, and can only be used after review by your team.

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