chore(ci): migrate GitHub Actions to OIDC auth#54
Open
jonthia-drift wants to merge 1 commit into
Open
Conversation
Replace long-lived AWS_ACCESS_KEY_* secrets with sts:AssumeRoleWithWebIdentity via GitHub OIDC. - Add workflow-level permissions (id-token: write, contents: read) - Replace aws-access-key-id/aws-secret-access-key with role-to-assume - Reference org-level vars AWS_DEPLOY_ROLE_PROD / AWS_DEPLOY_ROLE_NONPROD - Pin floating action refs to commit SHAs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replaces long-lived AWS_ACCESS_KEY_* secrets with short-lived STS credentials via GitHub OIDC.
Changes
permissions: { id-token: write, contents: read }aws-access-key-id/aws-secret-access-keywithrole-to-assume: ${{ vars.AWS_DEPLOY_ROLE_PROD/NONPROD }}Prerequisites before merge
AWS_DEPLOY_ROLE_PRODandAWS_DEPLOY_ROLE_NONPROD(role ARNs).subclaims (will be applied centrally as part of the migration).CI on this PR is expected to fail at the AWS credentials step until both of the above are in place.