{"version":"2.1.285","anchor":"bedrock-client-no-longer-resolves-default-credentials-and-s","canonical_anchor":"bedrock-client-no-longer-resolves-default-credentials-and-s","heading":"Bedrock connection no longer picks up default credentials on its own","tier":"notice","area":"Bedrock","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bedrock-client-no-longer-resolves-default-credentials-and-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Bedrock connection no longer picks up default credentials on its own\n\nThe Bedrock client now passes its options correctly, stops looking up default credentials by itself and identifies itself as AnthropicBedrock\/JS\n\n**Unclear.** Whether this client is the one Claude Code uses for your own Bedrock connection is not clear.\n\n**What**\n\nBedrock is Amazon's service for running Claude models. The client that talks to it has changed in three ways:\n\n- It no longer looks up default credentials automatically.\n\n- It now passes an empty API key and an optional sign-in token, and passes the rest of its options correctly; before, the wrong set of options was passed along.\n\n- It now identifies itself to the service as `AnthropicBedrock\/JS`.\n\n**Why**\n\nThis could change how Claude Code signs in to Bedrock, so it is worth watching if you use Bedrock.\n\n- Area: Bedrock\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}