AI PR Review fails because BEDROCK_ROLE_ARN is unavailable
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
Research direction
Start by reading the referenced Codex workflow at the pinned shared CI revision and the failed run’s AWS credential setup logs. Check how the caller passes secrets and which environment the review job uses, then verify the BEDROCK_ROLE_ARN configuration and OIDC trust. Done when both review jobs can assume the intended role and post their results after rerunning.
Written by the indexing model from the issue text.
Description
The AI PR Review workflow fails during AWS credential setup because BEDROCK_ROLE_ARN is unavailable to the review jobs. Both Codex and Claude stop before generating a review.
Affected run
- PR: #298 (
docs: add SDK 3 upgrade summaries) - Workflow run: https://github.com/aws/aws-durable-execution-docs/actions/runs/40571904578
- Codex job: https://github.com/aws/aws-durable-execution-docs/actions/runs/40571904578/job/122428039324
- Claude job: https://github.com/aws/aws-durable-execution-docs/actions/runs/40571904578/job/122428038230
- Event:
pull_request_target; the PR branch is in the same repository. - Shared workflow revision:
aws/aws-durable-execution-ci@ac55d9f4b027e193aba9fa5a69c70bfa1bdc38ed.
Evidence
Both Configure AWS credentials for Codex and Configure AWS credentials for Claude exhaust 12 retries and fail with:
Credentials could not be loaded, please check your action inputs:
Could not load credentials from any providers
The Codex workflow sets role-to-assume: ${{ secrets.BEDROCK_ROLE_ARN }} and runs in the ai-pr-review-runtime environment. The failed action's logged inputs contain no role-to-assume value.
A read-only check of secret names on October 27, 2026 found no BEDROCK_ROLE_ARN repository secret and no secrets in the ai-pr-review-runtime environment. The caller and nested reusable workflow already use secrets: inherit, and their job permissions include id-token: write.
Expected behavior and proposed resolution
Configure the intended Bedrock IAM role ARN as BEDROCK_ROLE_ARN in this repository's ai-pr-review-runtime environment or repository secrets, with the role's GitHub OIDC trust configured for the review job. Then rerun the failed jobs and verify both reviews execute and post their results.
A separate improvement in the shared CI repository would be an early check for an empty BEDROCK_ROLE_ARN, so a missing configuration produces a direct error instead of repeated credential-provider retries.
The reported failure occurs before either model runs; no AI review findings were produced for the documentation changes.
- Dominant language
- Python
- Stars
- 16
- Forks
- 15
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/aws-durable-execution-docs
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
[docs]: document remote debuggingPossibly taken @reginaldalfret claimed this 20 days ago. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws/aws-durable-execution-docs#248 · 1 comment ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in aws/aws-durable-execution-docs
Similar issues
-
backlog
Difficulty 1/5 Under an hour Newbie friendliness 91/100
EchoTools/nevr-runtime#1108 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
btclib-org/btclib-wallet#587 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Judgment-Pack/judgment-pack-spec#275 ·
Maintainers usually reply within 1 day