Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Revise AWS deployment workflow to use an assumed role rather than an access key pair #959

Open
asjohnston-asf opened this issue Apr 12, 2022 · 0 comments · May be fixed by #2523
Open

Revise AWS deployment workflow to use an assumed role rather than an access key pair #959

asjohnston-asf opened this issue Apr 12, 2022 · 0 comments · May be fixed by #2523

Comments

@asjohnston-asf
Copy link
Member

asjohnston-asf commented Apr 12, 2022 •
edited
Loading

We currently provision a github-actions IAM user with an AWS access key for github to use when deploying HyP3 via GitHub Actions. The configure-aws-credentials action now recommends provisioning an IAM role and granting the Github OIDC provider permission to assume that role, rather than using an access key pair:

https://github.com/aws-actions/configure-aws-credentials#usage
@jacquelynsmale jacquelynsmale linked a pull request Dec 11, 2024 that will close this issue
Draft
@jacquelynsmale jacquelynsmale linked a pull request Dec 11, 2024 that will close this issue
Refactor GitHub actions to use AWS Assumed Role #2523
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Refactor GitHub actions to use AWS Assumed Role ASFHyP3/hyp3
1 participant
@asjohnston-asf