{"version":"2.1.285","anchor":"aws-provider-chain-resolver-no-longer-honours-claude-code-sk","canonical_anchor":"aws-provider-chain-resolver-no-longer-honours-claude-code-sk","heading":"CLAUDE_CODE_SKIP_AWS_CRED_CACHE no longer turns off one AWS credential step","tier":"notice","area":"Bedrock","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/aws-provider-chain-resolver-no-longer-honours-claude-code-sk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### `CLAUDE_CODE_SKIP_AWS_CRED_CACHE` no longer turns off one AWS credential step\n\nClaude Code's AWS client now always uses its credential provider chain step, even when `CLAUDE_CODE_SKIP_AWS_CRED_CACHE` is set\n\n**Unclear.** The variable may still be read elsewhere, so how caching behaves with it set is unclear.\n\n**What**\n\nClaude Code's AWS client uses a step that goes through the places AWS credentials can come from. Before, that step was skipped when `CLAUDE_CODE_SKIP_AWS_CRED_CACHE` was set. Now it is always used, and a different step does the work.\n\n**Why**\n\nIf you set `CLAUDE_CODE_SKIP_AWS_CRED_CACHE`, credential caching may behave differently than you expect.\n\n- Area: Bedrock\n- Names: `CLAUDE_CODE_SKIP_AWS_CRED_CACHE`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}