{"version":"2.1.285","anchor":"setup-bedrock-command-now-hidden-when-a-provider-is-already","canonical_anchor":"setup-bedrock-command-now-hidden-when-a-provider-is-already","heading":"The setup-bedrock command has a new availability check","tier":"notice","area":"Bedrock","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/setup-bedrock-command-now-hidden-when-a-provider-is-already","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### The setup-bedrock command has a new availability check\n\nThe `setup-bedrock` command is now enabled only when a new check passes, as well as depending on `CLAUDE_CODE_USE_BEDROCK`\n\n**Unclear.** What the new check looks at, such as managed settings or a locked provider, is not known.\n\n**What**\n\nThe `setup-bedrock` command reconfigures Amazon Bedrock authentication, region and model pins. Amazon Bedrock is Amazon's service for running Claude models.\n\nWhether this command was hidden used to depend only on `CLAUDE_CODE_USE_BEDROCK`. It now also has a separate check that decides whether it is enabled.\n\n**Why**\n\nIf you use Bedrock, you may find `setup-bedrock` available in some setups and not in others.\n\n- Area: Bedrock\n- Names: `\/setup-bedrock`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}