GH-50899: [CI][C++] Use OIDC instead of ACCESS_KEY and SECRET_KEY for sccache's s3 creds - #51028
Draft
paultiq wants to merge 1 commit into
Draft
GH-50899: [CI][C++] Use OIDC instead of ACCESS_KEY and SECRET_KEY for sccache's s3 creds#51028paultiq wants to merge 1 commit into
paultiq wants to merge 1 commit into
Conversation
paultiq
requested review from
assignUser,
jonkeane,
kou and
raulcd
as code owners
August 28, 2026 21:54
|
|
paultiq
marked this pull request as draft
August 29, 2026 00:18
Contributor
Author
|
Per @kou 's comment #50899 (comment), leaving as draft. I only made change to one workflow file. The other github.*.yml files will need the same change. I tested this with |
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.
Rationale for this change
This PR moves crossbow builds to short-lived S3 credentials. It does this via GitHub's OIDC provider and an AWS ROLE_ARN with a trust relationship configured. This configuration is detailed here:
The benefits of short-lived / temporary credentials discussed further here: AWS Well-architected Framework Best Practices SEC02-BP02 Use temporary credentials
sccache supports a variety of S3 creds: S3 credentials
What changes are included in this PR?
Use AssumeRoleWithWebIdentity for sccache S3 credentials.
By assuming the AWS_ROLE_ARN, the sccache session relies on credentials that expire*, issued only to workflows in the trusted repository, and scoped to the sccache bucket.
Specific tasks:
aws-actions/configure-aws-credentials@v4step to the workflow.Separately, someone will need to add the role and trust to AWS:
* I can share an example if needed
Are these changes tested?
Yes, locally and on a fork.
Are there any user-facing changes?
No