Cause (Documented platform behavior): Local AWS default credential chain doesn't resolve within 60s; before v2.1.207 the request hung indefinitely.
Fix status: documented_behavior
Other error fragments:
- Timed out after 60s waiting for AWS. Check your network and proxy settings; if a credential helper needs longer to prompt you, raise CLAUDE_CODE_AWS_CHAIN_RESOLVE_TIMEOUT_MS.
- API Error: AWS default-chain credential resolve timed out
Evidence (public sources, summarized; not reproduced by this contributor):
- https://code.claude.com/docs/en/errors.md (official_docs, unknown, documented_behavior): Docs give exact messages, 60s limit, common causes (prompting credential_process, silent IMDS) and remedies, with version notes v2.1.207/v2.1.267.
Search phrasings: claude code bedrock credential resolve timed out; claude code aws sso hang; CLAUDE_CODE_AWS_CHAIN_RESOLVE_TIMEOUT_MS
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Requests fail after ~60s before reaching Bedrock.
- Context
- Product: Claude Code Component: Amazon Bedrock credential resolution Operation: Model request via Bedrock / Bedrock setup wizard Affected versions: message wording v2.1.267+; timeout added v2.1.207 Environment: Bedrock; containers/VMs without IMDS Trigger: AWS profile credential_process waits for input it can't receive, SSO needs browser sign-in, or a container/VM IMDS never answers.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- API Error: Could not load AWS credentials · AWS default-chain credential resolve timed out. Check or refresh your AWS credentials and try again.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Claude Code] 'API Error: Could not load AWS credentials · AWS default-chain credential resolve timed out' (Bedrock) from interactive credential_process or unreachable IMDS
Recommended action: Run `aws sts get-caller-identity` with the same AWS_PROFILE; do `aws sso login` before starting; raise CLAUDE_CODE_AWS_CHAIN_RESOLVE_TIMEOUT_MS only for legitimately slow interactive helpers (aws-vault + MFA).
Option: Pre-resolve credentials outside Claude Code [evidence: official_recommended_action]
Applies when: see problem
Steps:
1. aws sts get-caller-identity --profile <p>
2. aws sso login --profile <p>
3. Optionally set CLAUDE_CODE_AWS_CHAIN_RESOLVE_TIMEOUT_MS
Expected: Chain resolves from cache
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 10f7a33e-1039-49d1-9b9f-405438fb5367
- Proposed action
- Recommended action: Run `aws sts get-caller-identity` with the same AWS_PROFILE; do `aws sso login` before starting; raise CLAUDE_CODE_AWS_CHAIN_RESOLVE_TIMEOUT_MS only for legitimately slow interactive helpers (aws-vault + MFA). Option: Pre-resolve credentials outside Claude Code [evidence: official_recommended_action] Applies when: see problem Steps: 1. aws sts get-caller-identity --profile <p> 2. aws sso login --profile <p> 3. Optionally set CLAUDE_CODE_AWS_CHAIN_RESOLVE_TIMEOUT_MS Expected: Chain resolves from cache
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.