AWS Bedrock: Invalid Model - The model does not work with your plan or api key

[ngochip]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Bedrock doesn’t seem to be working. Cursor says invalid model even though my key and model are valid. I can use the key and model in Terminal with the aws command, but not in Cursor.

I used to be able to use it 2 months ago, but now I can’t. Tried factory reset and everything on the forum but no luck.

Steps to Reproduce

1. Enable AWS Bedrock in Model Settings
   Key: <my_key>
   secret: <my_secret>
   region: us-west-2

2. add custom model: global.anthropic.claude-sonnet-4-5-20250929-v1:0

3. create new chat. and got the error: The model global.anthropic.claude-sonnet-4-5-20250929-v1:0 does not work with your current plan or api key

Expected Behavior

Cursor should work with Bedrock

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.0-pre.0.patch.0 (Universal)
VSCode Version: 1.105.1
Commit: 7a7092b2be6de13075bff79c87f1ad3b4190b050
Date: 2025-11-19T08:16:13.881Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.5.0

For AI issues: which model did you use?

Sonnet 4.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report.

First, could you confirm your Cursor subscription status? BYOK requires a Pro plan. Is your Pro subscription active?

If you’re on Pro, please try the following:

• Model format: try using the regional format instead of the global prefix:

  Before: global.anthropic.claude-sonnet-4-5-20250929-v1:0
  After: us.anthropic.claude-sonnet-4-5-20250929-v1:0 (for us-west-2)

• Try a different region: another user fixed Bedrock errors by switching regions (for example, from eu-central-1 to eu-north-1).

Could you please share:

• Your Cursor subscription status
• A screenshot of your exact Bedrock model settings
• Confirmation that the model works in the AWS Bedrock console

This will help us understand whether the issue is related to format, region, quotas, or subscription.

[ngochip]

@deanrie,

1. I have a Pro subscription, and it is still working. Now I have reached the limit and am looking to use Bedrock as a temporary alternative.
2. I have tried:

• changing region (lots of regions)
• changing model (all types including Sonnet 3.7, 4, 4.5…)
• Changing global, us, eu…
• rm -rf ~/Library/Application\ Support/Cursor/User/globalStorage
  All did not work.

3. I use the same AWS key and model name on the terminal, and it works fine.

[deanrie]

Thanks for the detailed follow-up. Since your AWS credentials work fine via the CLI but not in Cursor, we need a bit more diagnostics to find the root cause.

Could you please share:

• Console logs: Open Developer Tools (Help > Toggle Developer Tools), go to the Console tab, try sending a message with your Bedrock model, and share any error messages that appear
• IAM permissions: Confirm that your AWS credentials have the following permissions:
  • bedrock:InvokeModel
  • bedrock:InvokeModelWithResponseStream

This will help us understand whether it is a Cursor BYOK validation issue or an AWS permission edge case that needs engineering investigation.

[ngochip]

Looks like the engineers did something.
I was going to try again to get the logs for you. But it worked without me changing any settings or configuration. LOL.
Note that I tried hundreds of times in the past few days and failed.
I think we need to keep it more stable.

Thanks anyway

[deanrie]

Great, I’m glad everything is working now.

Since the issue went away on its own without any config changes on your side, it suggests there might have been a temporary backend problem with Bedrock validation.

If you run into this again, please grab the console logs (Help > Toggle Developer Tools > Console tab) right when the error appears. That will help us find and fix the root cause.

Thanks for your patience and for reporting this.