feat: Migrate AWS credentials to OIDC and pin action SHAs#877
Merged
diegopazosrego merged 1 commit intoJun 11, 2026
Merged
Conversation
- Remove static AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY from all jobs - Refactor setup-env composite action: remove AWS credential inputs and configure-aws-credentials step (credential config now lives in calling workflow) - Add permissions: id-token: write at workflow level in deployment.yml - Add configure-aws-credentials with role-to-assume: AWS_ROLE_TO_ASSUME_STAGING directly in pr, deploy, and release jobs - Pin all action versions to full SHA hashes across all workflow files Part of INFSEC-1135.
luarx
approved these changes
Jun 11, 2026
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
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.
AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEYfrom all jobsAWS_ROLE_TO_ASSUME_STAGINGdirectly in pr, deploy, and release jobsPart of INFSEC-1135.