{"version":"2.1.285","anchor":"bedrock-client-auth-change","canonical_anchor":"bedrock-client-auth-change","heading":"Amazon Bedrock connections pass the API key differently","tier":"internal","area":"Bedrock","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bedrock-client-auth-change","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Amazon Bedrock connections pass the API key differently\n\nWhen connecting to Amazon Bedrock, Claude Code now passes a different API key value and explicitly sends no separate auth token\n\n**Unclear.** It is not clear which setting the API key now comes from, or whether sign-in with `AWS_BEARER_TOKEN_BEDROCK` behaves differently.\n\n**What**\n\nAmazon Bedrock is Amazon's cloud service for running Claude models. When Claude Code sets up its connection to Bedrock, it now takes the API key from a different value, leaves it empty when there is none, and explicitly sets no separate auth token.\n\n**Why**\n\nThis may change how Claude Code signs in to Bedrock when you use a bearer token, a key sent with each request.\n\n- Area: Bedrock\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}