{"version":"2.1.224","anchor":"two-warnings-when-a-bedrock-region-prefix-cannot-be-confirme","canonical_anchor":"two-warnings-when-a-bedrock-region-prefix-cannot-be-confirme","heading":"Two warnings when a Bedrock region prefix cannot be confirmed","tier":"notice","area":"Bedrock","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/two-warnings-when-a-bedrock-region-prefix-cannot-be-confirme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Two warnings when a Bedrock region prefix cannot be confirmed\n\nBedrock now warns when it can't confirm a region prefix, or when models resolve elsewhere.\n\n**What**\n\nIf inference-profile discovery is unavailable, setting a region prefix now warns that it is being applied without an availability check. If discovery works but some models resolve to a different region, a second warning names how many and states that the prefix is a preference, not a residency guarantee.\n\n**Details**\n\n- Warning text is assembled at runtime around the fixed fragment \"is being applied without an availability check (inference-profile discovery is unavailable).\"\n- Both warnings only appear when `ANTHROPIC_BEDROCK_REGION_PREFIX` is set.\n\n**Evidence**\n\n`This is a preference, not a residency guarantee.`\n\n- Area: Bedrock\n- Names: `ANTHROPIC_BEDROCK_REGION_PREFIX`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}