ci: grant id-token write permission for AWS OIDC#8
Merged
Conversation
The Build and Release workflow's Configure AWS Credentials step assumes a role via OIDC (role-to-assume with no static keys), which requires the id-token: write permission. The workflow only granted contents: read, so the step would fail to obtain a web identity token. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 15, 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
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.
Problem
The
Build and Releaseworkflow's Configure AWS Credentials step assumes an IAM role via OIDC (role-to-assumewith no static access keys). That flow requires theid-token: writepermission so the runner can mint a web-identity token, but the workflow only grantedcontents: read. The step would fail to authenticate to AWS.This is the latent second failure observed in run 27558649432 — it would surface right after the Docker Hub login step is unblocked.
Change
Add
id-token: writeto the top-levelpermissions:block.Note
This PR does not fix the current
Login to Docker Hubfailure (Password required). That is a provisioning issue — the org secretDOCKERBUILDBOT_READ_PATis not shared withdocker/envoy. Tracking that separately with infra (admin needs to grant repo access to the org secret).🤖 Generated with Claude Code