[BUG] v2.1.94 breaks Bedrock Bearer Token auth - "Authorization header is missing"
Resolved 💬 3 comments Opened Apr 8, 2026 by learsea Closed Apr 8, 2026
Environment
- Claude Code version: 2.1.94 (regression from 2.1.92)
- Platform: macOS (Darwin 25.4.0, arm64)
- Auth method:
AWS_BEARER_TOKEN_BEDROCKenvironment variable - Model:
global.anthropic.claude-opus-4-6-v1 - Region:
us-east-1
Bug Description
After upgrading from v2.1.92 to v2.1.94, all Bedrock API calls fail with:
API Error: 403 {"Message":"Authorization header is missing"}
v2.1.92 works fine with the exact same environment variables and configuration.
Steps to Reproduce
- Set environment variables:
``bash``
export CLAUDE_CODE_USE_BEDROCK=1
export AWS_BEARER_TOKEN_BEDROCK=<your_token>
export AWS_REGION=us-east-1
export ANTHROPIC_MODEL=global.anthropic.claude-opus-4-6-v1
- Run v2.1.94:
``bash``
/path/to/2.1.94 -p "say hello"
- Observe 403 error:
Authorization header is missing
Expected Behavior
The Bearer Token from AWS_BEARER_TOKEN_BEDROCK should be sent as the Authorization header in Bedrock API requests, as it works in v2.1.92.
Actual Behavior
v2.1.94 does not include the Authorization header in the request, causing a 403 rejection from Bedrock.
Workaround
Roll back to v2.1.92.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗