Support AWS Bedrock API Key (Instead of Access Key / Secret Key)

Feature Requests
1

Hi Cursor team,

Right now, the only way to integrate Bedrock into Cursor is by supplying AWS access key + secret key, or setting up a temporary IAM role. While this works, it comes with some downsides:

  • Security: Long-lived IAM credentials are harder to manage and pose risks if leaked.
  • Developer experience: Managing IAM roles and external IDs is non-trivial for frontend-focused workflows.
  • Least privilege: With the new Bedrock API Key, we can tightly scope model access, without broader AWS permissions.

Suggested improvement

Amazon recently added native API Key support for Bedrock, which:

  • Allows calling models like Claude via Authorization: Bearer <key>;
  • Supports fine-grained access control (by model, user, context);
  • Doesn’t require managing AWS credentials or roles.

Would love to see Cursor adopt this – maybe allow pasting the Bedrock API Key directly into the “Models → API Keys” UI, similar to how OpenAI keys are handled.

Thanks!

7 Likes
2

Hey, thanks for the feature request, we’ll consider it.

3 Likes
3

+1, feels like a no-brainer. Hope you guys implement this.

1 Like
4

any progress on it?

5

+1. Must have feature

1 Like
6

+1

7

My org has a policy enforcing MFA. I need to pass in session token as well to use Bedrock using Access Key. Any idea if that will be added in? Cline already has it

8

Can we get support for this? It’s holding me back from using cursor