Skip to content
Terragrunt Reference Architecture
HCL Shell
Branch: master
Clone or download
Latest commit 3480529 Nov 1, 2019


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Added FUNDING.yml Nov 1, 2019
acme-master Initial commit May 7, 2019
acme-prod Initial commit May 7, 2019
acme-staging Initial commit May 7, 2019
common Initial commit May 7, 2019
modules/empty Initial commit May 7, 2019
.editorconfig Initial commit May 7, 2019
.gitignore Initial commit May 7, 2019
.pre-commit-config.yaml Initial commit May 7, 2019
LICENSE Initial commit May 7, 2019 Initial commit May 7, 2019 Initial commit May 7, 2019

Acme's Infrastructure - Terragrunt Reference Architecture

This repository contains rather complete infrastructure configurations where Terragrunt is used to manage infrastructure for Acme Corporation.

By the way!

This code is very close to the one produced by - open-source infrastructure as code generator from visual diagrams created with


Acme has several environments (prod, staging and dev) entirely separated by AWS accounts.

Infrastructure in each environment consists of multiple layers (autoscaling, alb, vpc, ...) where each layer is configured using one of Terraform AWS modules with arguments specified in terraform.tfvars in layer's directory.

Terragrunt is used to work with Terraform configurations which allows to orchestrate dependent layers, update arguments dynamically and keep configurations DRY.


Primary AWS region for all environments is eu-central-1 (Frankfurt):

  • acme-prod - Production configurations (AWS account - 111111111111)

  • acme-staging - Staging configurations (AWS account - 444444444444)

  • acme-master - Master AWS account (333333333333) contains:

    • AWS Organizations
    • IAM entities (users, groups)
    • ECR repositories
    • Route53 zones


If you are using Mac you can install all dependencies using Homebrew:

$ brew install terraform terraform-docs terragrunt pre-commit direnv
$ brew install

AWS accounts and IAM relations

Acme has dedicated AWS account where IAM users, groups and roles are managed. This AWS account is used as a jump account, where IAM users are logged in and then they assume role in other AWS account.

AWS access credentials should be set using environment variables:

$ export AWS_DEFAULT_REGION=eu-central-1
$ export AWS_ACCESS_KEY_ID=...

aws-vault, vaulted or other tool can be used to manage your AWS credentials securely locally and switch roles.

How to use it?

Go to directory for the environment and region you want to work with:

$ cd acme-staging/eu-central-1

Initialize the dependencies (download providers and modules). This command is enough to run once:

$ terragrunt init

To create infrastructure in all layers in a single region:

$ terragrunt apply-all

Alternatively, you can create infrastructure in a single layer (eg, vpc):

$ cd vpc
$ terragrunt apply

See official Terragrunt documentation for all available commands and features.


This project is created and maintained by Anton Babenko.

Maintained by Anton Babenko @antonbabenko


This work is licensed under MIT License. See LICENSE for full details.

Copyright (c) 2019 Anton Babenko

You can’t perform that action at this time.