{"version":"2.1.287","anchor":"bedrock-gateway-gives-a-clearer-error-for-invalid-model-ids","canonical_anchor":"bedrock-gateway-gives-a-clearer-error-for-invalid-model-ids","heading":"Clearer error when a Bedrock model id is rejected","tier":"notice","area":"Bedrock","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/bedrock-gateway-gives-a-clearer-error-for-invalid-model-ids","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Clearer error when a Bedrock model id is rejected\n\nWhen AWS rejects a model id as invalid, the Bedrock gateway now returns an error saying the model is not available and how to map it\n\n**Unclear.** It is not clear which gateway product this applies to.\n\n**What**\n\nAmazon Bedrock is AWS's service for running models. When AWS rejects a model id as invalid, Claude Code's Bedrock gateway now logs the problem and returns a 400 error (a \"bad request\" error) saying the model is not available on Bedrock. The message tells whoever runs the gateway to map the model under `models:` to a Bedrock model id or inference profile.\n\n**Why**\n\nA wrong model mapping in the gateway's setup is now much easier to spot and fix.\n\n- Area: Bedrock\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5"}