{"version":"2.1.96","anchor":"bedrock-bearer-token-authentication-streamlined","canonical_anchor":"bedrock-bearer-token-authentication-streamlined","heading":"Bedrock bearer token authentication streamlined","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.96\/e\/bedrock-bearer-token-authentication-streamlined","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.96","markdown":"### Bedrock bearer token authentication streamlined\n\n**What**\n\nBearer token authentication for AWS Bedrock has been refactored to use the SDK's native `apiKey` parameter instead of manually setting `skipAuth: true` and injecting an `Authorization` header.\n\n**Details**\n\n- Previously, when using `AWS_BEARER_TOKEN_BEDROCK`, Claude Code would set `skipAuth: !0` and manually add `Authorization: Bearer <token>` to the request headers. This has been simplified to pass the token directly as `apiKey`, which is the SDK's standard mechanism.\n- When `CLAUDE_CODE_SKIP_BEDROCK_AUTH` is enabled, the code now properly extracts and preserves any existing `Authorization` header from `defaultHeaders` configuration. Previously, custom authorization headers in `defaultHeaders` could be ignored in certain code paths.\n- The `skipAuth` flag is now only set when `CLAUDE_CODE_SKIP_BEDROCK_AUTH` is enabled *and* no bearer token is available (previously it was set whenever either the skip flag or a bearer token was present).\n\n**Evidence**\n\nBedrock client construction refactored across three code paths (search for `apiKey: Y.token`, `apiKey: process.env.AWS_BEARER_TOKEN_BEDROCK`, and the new `pq_` helper that extracts authorization headers)"}