{"version":"2.1.315","anchor":"provider-refusal-detection-broadened-for-bedrock-and-vertex","canonical_anchor":"provider-refusal-detection-broadened-for-bedrock-and-vertex","heading":"Clearer errors when Bedrock or Vertex refuses access to a model","tier":"notice","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/provider-refusal-detection-broadened-for-bedrock-and-vertex","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Clearer errors when Bedrock or Vertex refuses access to a model\n\nClaude Code now recognises more Bedrock and Vertex errors as a refusal to give you access to a model\n\n**What**\n\nClaude Code can use Claude models through cloud providers such as Amazon Bedrock and Google Vertex AI. It now recognises more of their errors as the provider refusing access to a model:\n\n- Bedrock: more access-denied responses are matched.\n\n- Vertex: a \"failed precondition\" error about a publisher model now counts as a refusal. Before, only a \"not found\" error did.\n\n- Vertex: \"publisher model\" is now matched however it is capitalised.\n\n**Why**\n\nIf your account cannot use a model on Bedrock or Vertex, you are more likely to get a clear model-access error instead of a general one.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}