Feature: Adds AWS Cognito OIDC Support #1762
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Implements an additional method for AWS OIDC that allows a project to leverage AWS Cognito Identity Pool to chain to AWS for deployments.
The reason for this extra step is well documented on this site:
https://catnekaise.github.io/
As it stands today, the exchange of identity between GitHub Actions and AWS IAM only allows
aud
andsub
claims to be passed. If you want to lock down deployments more using other claims in the Github JWT it is not possible. By using a cognito identity custom mapping claims to attributes becomes possible allowing more secure limitations on Github Action assumed roles.A walkthrough on how to set up a cognito identity pool with github action tokens as a provider can be found at https://catnekaise.github.io/github-actions-abac-aws/setup-using-aws-console/
Once the identity pool is set up and custom mapping performed you can then restricted Trust Policies by GitHub claims via PrincipalTags.
To use this, it requires new configuration options to be added to the digger.yml see below: