Bug: Bedrock: model not found

[Marina_Olivella]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using any AWS Bedrock model, Cursor returns:
Model name is not valid: “us.anthropic.claude-opus-4-5-20251101-v1:0”
or
The provided model identifier is invalid.
This worked until recently and then stopped, with no changes to AWS config or credentials. All Bedrock models fail, including ones that previously worked.

Steps to Reproduce

Enable AWS Bedrock in Cursor settings
Use region us-west-2
Enter valid AWS access key ID and secret
Set model ID to any of the tested IDs below
Attempt to use the model (chat/composer)
Model IDs tested (all fail)
openai.gpt-oss-120b-1:0
us.anthropic.claude-opus-4-5-20251101-v1:0
anthropic.claude-opus-4-5-20251101-v1:0
claude-opus-4-5-20251101-v1:0
anthropic.claude-opus-4-6-v1
anthropic.claude-opus-4-1-20250805-v1:0
AWS CLI verification
The models are available and list correctly:
aws bedrock list-foundation-models --region us-west-2 --by-provider anthropic | grep -i opus
Example output includes:
anthropic.claude-opus-4-6-v1
anthropic.claude-opus-4-1-20250805-v1:0
anthropic.claude-opus-4-5-20251101-v1:0

Expected Behavior

The Bedrock models should be usable in Cursor, as it was before.

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 2.4.31
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Linux x64 6.8.0-94-generic

For AI issues: which model did you use?

anthropic.claude-opus-4-6-v1
anthropic.claude-opus-4-1-20250805-v1:0
anthropic.claude-opus-4-5-20251101-v1:0
global.anthropic.claude-opus-4-6-v1
us.claude-opus-4-1-20250805-v1:0
openai.gpt-oss-120b-1:0

Additional Information

Same credentials work with Bedrock outside Cursor (e.g. AWS CLI)
Config was working until roughly last week
No changes to AWS IAM or Bedrock model access
Suggests a regression in Cursor’s Bedrock integration

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, this is a known issue with Bedrock model name validation in the 2.4 branch. It used to reproduce only on Early Access, but it looks like it’s made its way into stable.

Previous report with the same error: AWS Bedrock model - ERROR_BAD_MODEL_NAME

The team is aware of the issue. I’ve forwarded your report to help raise the priority since the bug now affects the stable release.

Unfortunately, there isn’t a specific workaround right now. It worked correctly on 2.3.x. I’ll share updates as soon as I have them.