{"version":"2.1.319","anchor":"gateway-config-validation-gains-new-warnings-bedrock-guardr","canonical_anchor":"gateway-config-validation-gains-new-warnings-bedrock-guardr","heading":"Gateway settings checks warn about five more misconfigurations","tier":"notice","area":"LLM Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/gateway-config-validation-gains-new-warnings-bedrock-guardr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Gateway settings checks warn about five more misconfigurations\n\nClaude Code's gateway now warns about guardrail headers, GovCloud mixing, base URL variables, pooled priority and model mappings\n\n**What**\n\nClaude Code's gateway routes requests to model providers such as Amazon Bedrock and Google Cloud's Agent Platform (Vertex). Its check of managed settings, the settings an administrator sets centrally, now warns about:\n\n- An `X-Amzn-Bedrock-GuardrailIdentifier` header, which the gateway does not pass on to Bedrock, so it has no effect unless a Bedrock upstream sets `guardrail:`.\n\n- `admin.pooled_priority_order` set while `admin.pooled_conflict_rule` is not `priority_list`, in which case it is ignored.\n\n- A model mapped to upstreams outside the policies that list it.\n\n- GovCloud upstreams that share developers with non-GovCloud upstreams.\n\n- `ANTHROPIC_BEDROCK_BASE_URL` or `ANTHROPIC_VERTEX_BASE_URL` in the gateway's environment applying to upstreams that have no `base_url` of their own.\n\nAn upstream is one of the provider endpoints the gateway sends requests to.\n\n**Why**\n\nGateway operators find out early about settings that quietly do nothing, or that could send traffic across a GovCloud boundary they meant to keep separate.\n\n- Area: LLM Gateway\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}