Remove deprecated bedrock model slugs#919
Conversation
Audited all 132 Bedrock models by invoking each through the gateway with the CI
credentials and cross-checking against `aws bedrock list-foundation-models` /
`list-inference-profiles` (us-east-1). Removed 29 entries that are definitively
non-invocable and not fixable to a valid slug:
- Bedrock end-of-life (HTTP 404 "reached the end of its life"): the amazon.titan
text models, cohere.command-light/-text-v14, and the retired Claude 3.x /
original Claude 4 (2025-05-14) snapshots (anthropic. and us. variants).
- Invalid identifiers with no valid AWS id in any region (HTTP 400 "provided
model identifier is invalid"): meta.llama3-1-405b-instruct-v1:0 (+us.),
qwen.qwen3-235b-a22b-2507-v1:0, qwen.qwen3-coder-480b-a35b-v1:0,
deepseek.v3-v1:0 (superseded by deepseek.v3.2, which is valid and kept), and
the apac./eu. Claude 3.x cross-region profiles (which don't exist).
All 29 were bedrock-only, so the entries + their index.ts mappings were dropped.
Verified after removal: kept models still invoke (us.anthropic.claude-sonnet-4-6,
deepseek.v3.2, us.deepseek.r1-v1:0 all 200); removed ids now 404 as unknown.
NOT touched (need separate handling, not slug bugs): access-denied "Legacy"
models (account-scoped — may work elsewhere: claude-3-haiku/-sonnet, cohere
command-r, us.meta.llama3-2-*), region-scoped eu. profiles with a valid base
(eu.mistral.pixtral-large-2502, eu.meta.llama3-2-*), the Bedrock-Mantle
openai.gpt-5.x / xai.grok-4.3 ("Unexpected field type" — a proxy routing issue),
and global.anthropic.claude-fable-5 (data-retention config).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Follow-up to the Bedrock cleanup. These 11 entries return HTTP 404 "Access denied. This Model is marked by provider as Legacy and you have not been granted access" on invocation — AWS has flagged them Legacy and no longer grants access on new accounts, so they are effectively unusable via the proxy. All bedrock-only: - anthropic.claude-3-haiku-20240307-v1:0 / -3-sonnet-20240229-v1:0 (+ us.) - us.anthropic.claude-sonnet-4-20250514-v1:0 - cohere.command-r-v1:0 / command-r-plus-v1:0 - us.meta.llama3-2-1b/3b/11b/90b-instruct-v1:0 Removed the entries + their index.ts mappings. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 420a823ecd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
| "us.anthropic.claude-sonnet-4-20250514-v1:0": ["bedrock"], | ||
| "anthropic.claude-3-7-sonnet-20250219-v1:0": ["bedrock"], | ||
| "us.anthropic.claude-3-7-sonnet-20250219-v1:0": ["bedrock"], | ||
| "anthropic.claude-haiku-4-5-20251001-v1:0": ["bedrock"], |
There was a problem hiding this comment.
As of July 6, 2026, AWS still documents us.anthropic.claude-sonnet-4-20250514-v1:0 as a valid Geo Inference ID for Claude Sonnet 4, with Converse/Invoke support and an EOL date of October 14, 2026 (AWS model card). Removing this catalog entry and its AvailableEndpointTypes mapping means callers that explicitly use the US Bedrock inference profile no longer resolve to bedrock and can fall back to the wrong provider/secret path even though the upstream model is still available.
Useful? React with 👍 / 👎.
| "bedrock" | ||
| ] | ||
| }, | ||
| "qwen.qwen3-coder-30b-a3b-v1:0": { |
There was a problem hiding this comment.
AWS's current Bedrock model card lists qwen.qwen3-235b-a22b-2507-v1:0 with lifecycle Active, no EOL, and bedrock-runtime Invoke/Converse access (AWS model card). Since this commit removes the model from both the static catalog and endpoint mapping, users requesting the documented Bedrock runtime ID are treated as unsupported despite the upstream model still being available.
Useful? React with 👍 / 👎.
1 participant
bedrock doesn't provide a model list endpoint, and so the deprecation job doesn't easily work with it. I just did a pass over the bedrock endpoints and removed the ones that don't invoke.