Authenticating to AWS accounts
Pipelines can intelligently figure out which AWS account to authenticate to based on the infrastructure changes proposed in your Pull Request.
How Pipelines authenticates to AWS
To perform the actions that Pipelines detects, each AWS account needs to assume an AWS IAM Role using OIDC. To explain OIDC at a high level, AWS considers GitHub an "identity provider," trusts GitHub's request for a temporary IAM Role, and then issues AWS credentials that are valid for the duration of a GitHub Action workflow.
Every time you create a new AWS account, you need to update the AWS OIDC configuration to create an IAM role for this account and allow it to be assumed by GitHub. When you use Gruntwork Landing Zone, this role is automatically created when adding a new AWS account.
How Pipelines knows what AWS account to authenticate to
Pipelines assumes that each top level directory in your
infrastructure-live repository maps to a single AWS account, excluding the directory used for module defaults. Each account-mapped directory must have an entry in the
/accounts.yml file with a key matching the directory name and containing key/value pairs for the AWS account ID and the account's root user email address.
For example, the following entry in
accounts.yml would be mapped to a directory called
my-cool-account in your
│ └── services
│ └── my-app.hcl
│ └── us-east-1
│ └── dev
│ └── database
│ └── terragrunt.hcl
AWS account authentication when creating new AWS accounts
This section contains some advanced topics pertaining to Pipelines, how it differentiates between types of changes, and how it handles planning and applying changes.
From the perspective of the end user, you will still only need one step in your CI job. Pipelines knows how to do the rest.
Pipelines can handle two main types of infrastructure-change events:
- Adding/changing/deleting Terragrunt files
- Creating new AWS accounts
For the first type of infrastructure change (add/change/delete Terragrunt files) Pipelines authenticates to the specific AWS account where the affected resources live. For the second type of change (creating new AWS accounts), Pipelines uses the Gruntwork Landing Zone Management Account.
Gruntwork Landing Zone Management Account
Gruntwork Landing Zone is built on top of AWS Control Tower, and AWS Control Tower requires that you create new AWS accounts using the Control Tower Management AWS Account.
When new AWS account requests are approved and the AWS account is created, Pipelines will create a Pull Request that contains an account baseline. Since Pipelines does not yet have access to the AWS account, the baseline will be applied by authenticating to the Management Account.
When applying the baseline and provisioning the Pipelines role in the new child account, Pipelines will first assume the management account Pipelines role, then will assume an automatically provisioned role in the child account (this process is known as role chaining). Once Pipelines has temporary credentials in the new account, it will run a plan or apply to provision the requested resources. After the initial baseline and Pipelines role has been applied in the child account, all subsequent events for that account will be handled by the Pipelines role directly in the child account.
The AWS IAM Role for the management account must have permissions to provision new AWS Accounts (via AWS Control Tower) and assume a role in all child accounts.
Each child account (e.g.,
prod, etc.) contains an AWS IAM role that Pipelines can assume from GitHub Actions using OIDC. This role is automatically provisioned as a part of the account baseline process. Once this role is in place in the child account, users may submit Pull Requests to add/modify/delete resources in the child account.
When a Pull Request is created or synchronized, or a push to the
main branch occurs, Pipelines will detect the changes, map them to the new account, assume the role in the child account, then run a
terragrunt plan or
terragrunt apply job (plan for PRs, apply for pushes to main).