Hi everyone,
I’m trying to better understand how Cursor behaves when integrating with AWS Bedrock, and I’m a bit confused about which quotas are actually being consumed.
Here’s my situation:
-
I configured AWS Bedrock as a provider in Cursor
-
When using Cursor, I selected both Auto and also tested Premium
-
However, I noticed that my “Auto” quota inside Cursor is still being consumed
This raised a couple of questions for me:
-
When Bedrock is configured, does using Auto still rely on Cursor’s own models/providers, or should it route through my Bedrock account?
-
If requests are actually going through Bedrock, is it expected that my Cursor Auto quota is still consumed?
-
What is the exact difference in routing/consumption between Auto vs Premium vs explicitly using a Bedrock model?
My expectation was that once Bedrock is configured, the usage would primarily reflect on my AWS side (quota/billing), but the fact that Cursor’s internal quota is being consumed made me unsure about what’s actually happening under the hood.
If anyone has clarity on how this routing works or best practices to ensure Bedrock is actually being used, I’d really appreciate it.
Thanks!