{"version":"2.1.285","anchor":"aws-client-credentialsconfigprofile-ignored-with-warning","canonical_anchor":"aws-client-credentialsconfigprofile-ignored-with-warning","heading":"Amazon Bedrock now checks environment credentials first","tier":"notice","area":"Bedrock","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/aws-client-credentialsconfigprofile-ignored-with-warning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Amazon Bedrock now checks environment credentials first\n\nBedrock sign-in now tries AWS keys from environment variables first, and ignores `credentials`, `config` and `profile` with a warning\n\n**What**\n\nWhen Claude Code uses Amazon Bedrock, it looks for AWS credentials, the keys that prove who you are to AWS, in several places in turn. It now tries credentials set in environment variables first.\n\nThe AWS client also no longer accepts three options:\n\n- `credentials`\n\n- `config`\n\n- `profile`\n\nIf any of them is given, Claude Code ignores it and warns that it is not supported.\n\n**Why**\n\nIf you use Bedrock and have AWS keys set in your environment, those keys are now picked before other sources. If you relied on one of the three options above, it no longer has any effect.\n\n- Area: Bedrock\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}