Skip to content

[skip-changelog] use OIDC to retrieve the credentials #901

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.

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

Merged
merged 1 commit into from
Feb 27, 2024
Merged

[skip-changelog] use OIDC to retrieve the credentials #901

merged 1 commit into from
Feb 27, 2024

Conversation

umbynos
Copy link
Contributor

@umbynos umbynos commented Feb 15, 2024

Please check if the PR fulfills these requirements

  • The PR has no duplicates (please search among the Pull Requests
    before creating one)
    - [ ] Tests for the changes have been added (for bug fixes / features)
  • What kind of change does this PR introduce?

Infra change

  • What is the current behavior?

We currently use statically generated credentials to access to s3 buckets.

  • What is the new behavior?

OpenID Connect allows workflows to exchange short-lived tokens directly from your cloud provider (see here)

  • Does this PR introduce a breaking change?

Nop

  • Other information:

@umbynos umbynos added the topic: infrastructure Related to project infrastructure label Feb 15, 2024
@umbynos umbynos self-assigned this Feb 15, 2024
- name: configure aws credentials
uses: aws-actions/configure-aws-credentials@v4
with:
role-to-assume: ${{ secrets.AWS_ROLE_TO_ASSUME }}
Copy link
Contributor Author

@umbynos umbynos Feb 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been added to the environment production

Comment on lines -13 to -14
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
Copy link
Contributor Author

@umbynos umbynos Feb 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • TODO remove these from the secrets

@per1234 per1234 added the type: enhancement Proposed improvement label Feb 15, 2024
Copy link

@michelangelomo michelangelomo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

TODO remove AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY from secrets
TODO add AWS_ROLE_TO_ASSUME to secrets
@umbynos umbynos merged commit 4b8a537 into main Feb 27, 2024
@umbynos umbynos deleted the OIDC branch February 27, 2024 08:34
umbynos added a commit that referenced this pull request Feb 27, 2024
@umbynos umbynos mentioned this pull request Feb 27, 2024
2 tasks
umbynos added a commit that referenced this pull request Feb 27, 2024
* followup of #901, fix CI

* fix permissions

* fix environment

* set permissions for the entire workflow

* replace create-release deprecated action with the same one used in the cli

* do not configure credentials when in pre-release (they are not used)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants