{"version":"2.1.283","anchor":"gateway-config-a-mantle-upstream-must-list-its-models","canonical_anchor":"gateway-gains-mantle-bedrock-mantle-and-anthropicgoogle","heading":"Gateway adds Bedrock Mantle and Google Cloud upstreams and a per-upstream models list","tier":"use","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/gateway-config-a-mantle-upstream-must-list-its-models","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Gateway adds Bedrock Mantle and Google Cloud upstreams and a per-upstream models list\n\nThe self-hosted gateway gains mantle and anthropicGoogleCloud upstreams, and each upstream's models list now controls which models it serves\n\n**Unclear.** Where this check runs, and whether mantle upstreams are themselves new, is not known.\n\n**What**\n\nThe self-hosted model gateway sits between Claude Code and the model provider and forwards requests to one or more upstreams. An upstream is a provider endpoint the gateway sends requests to. The gateway config now accepts two new upstream providers, and upstreams can be limited to a list of models.\n\n- `mantle` (AWS Bedrock Mantle): Needs a region and at least one entry in `models`. The list holds the models your AWS account has on Mantle, named as clients send them, for example `models: [claude-opus-4-7, claude-haiku-4-5]`. Only those models go to this upstream.\n\n- Defaults to `https:\/\/bedrock-mantle.<region>.api.aws\/anthropic`.\n\n- Signs in with an AWS bearer token, an access key and secret, or AWS's default credential chain. `aws_access_key_id` and `aws_secret_access_key` must be set together, and both are required with `aws_session_token`.\n\n- `CLAUDE_CODE_SKIP_AWS_CRED_CACHE` skips the cached credential lookup.\n\n- Validation rejects a mantle upstream placed beside a bedrock upstream that has a guardrail.\n\n- `anthropicGoogleCloud`: Needs `project_id` and `workspace_id`. `location` defaults to global.\n\n- Signs in with `access_token` or Google's own sign-in, optionally with `service_account_json`.\n\n- Per-upstream `models` list: when choosing where to send a model, the gateway first checks the upstream's optional `models` list, matching without regard to capitals or by the model's canonical id. A model not on the list is skipped with an error such as \"is not served by upstream\". Before, there was no such filter.\n\n- New config warnings cover Mantle model entries that route nowhere, mappings that never apply, and bedrock per-developer attribution not carrying over to Mantle.\n\n**Why**\n\nGateway operators can now route to Bedrock Mantle and Google Cloud's Anthropic endpoint, and send each model only to the upstreams that serve it. A mantle upstream without a `models` list is a config error, so add one when you set it up.\n\n- Area: Gateway\n- Names: `models`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}