{"version":"2.1.285","anchor":"bedrock-credential-cache-env-var-no-longer-honoured","canonical_anchor":"bedrock-credential-cache-env-var-no-longer-honoured","heading":"Gateway's Bedrock connection ignores CLAUDE_CODE_SKIP_AWS_CRED_CACHE","tier":"notice","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bedrock-credential-cache-env-var-no-longer-honoured","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Gateway's Bedrock connection ignores `CLAUDE_CODE_SKIP_AWS_CRED_CACHE`\n\nThe gateway's Bedrock connection now always uses the AWS credential lookup, even when CLAUDE_CODE_SKIP_AWS_CRED_CACHE is set\n\n**Unclear.** It is not clear which other places still honour the variable.\n\n**What**\n\nWhen the gateway connects to Amazon Bedrock, setting `CLAUDE_CODE_SKIP_AWS_CRED_CACHE` used to stop it from attaching its AWS credential lookup to the connection. That lookup is now always attached on this path, whatever the variable says. Other parts of Claude Code still read the variable.\n\n**Why**\n\nIf you relied on `CLAUDE_CODE_SKIP_AWS_CRED_CACHE` to avoid cached AWS credentials when using Bedrock through the gateway, that setting no longer applies there.\n\n- Area: Gateway\n- Names: `CLAUDE_CODE_SKIP_AWS_CRED_CACHE`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}