claude-code - 💡(How to fix) Fix [BUG] Anthropic API Error: Authorization header is missing with Bedrock Bearer Token [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#60587Fetched 2026-05-20 03:54:41
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×5commented ×2

Error Message

All of a sudden I've started getting a "Authorization header is missing" error when using a Bedrock Bearer Token.

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Bug Description All of a sudden I've started getting a "Authorization header is missing" error when using a Bedrock Bearer Token.

IMPORTANT Note - When I try to login with Amazon CLI configured env vars, it was not working for the past 2 hours - and all of a sudden it is now working for AWS CLI configured env vars for the same user. It still fails for Bedrock Bearer Token.

Side note - I just setup openclaw on my system, and I think it has cause some conflict issue for env

Environment Info Platform: Windows 11 Terminal: powershell Version: 2.1.144 (Claude Code)

What Should Happen?

Successful authentication

Error Messages/Logs

Steps to Reproduce

API key shows:

/setup-bedrock

──────────────────────────────────────────────────────────────────────────────── Set up AWS Bedrock Verification failed

✘ API key was rejected. Your IAM policy may be missing bedrock:CallWithBearerToken or bedrock:InvokeModel.

❯ 1. Go back and fix
2. Save anyway (skip verification)

↑↓ to navigate · Enter to select · Esc to go back

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.124

Claude Code Version

2.1.144

Platform

AWS Bedrock

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

<img width="1768" height="742" alt="Image" src="https://github.com/user-attachments/assets/5be06829-8620-4039-b8a0-4981cfa063eb" />

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING