# When AWS bedrock is enabled fallback non bedrock models to default invocation

**URL:** <https://forum.cursor.com/t/when-aws-bedrock-is-enabled-fallback-non-bedrock-models-to-default-invocation/161035>\
**Category:** Feature Requests\
**Tags:** byok\
**Created:** [May 19, 2026, 4:45pm UTC](https://forum.cursor.com/t/when-aws-bedrock-is-enabled-fallback-non-bedrock-models-to-default-invocation/161035 "2026-05-19T16:45:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![XavierHarkonnen2026](https://avatars.discourse-cdn.com/v4/letter/x/f6c823/32.png) [@XavierHarkonnen2026](https://forum.cursor.com/u/XavierHarkonnen2026)\
**Post date:** [May 19, 2026, 4:45pm UTC](https://forum.cursor.com/t/when-aws-bedrock-is-enabled-fallback-non-bedrock-models-to-default-invocation/161035/1 "2026-05-19T16:45:34Z")

</div>

### Feature request for product/service

AI Models

### Describe the request

It is so annoying to have to go into the ux models and have to toggle off aws bedrock to use a model that isnt on bedrock yet. i want cursor to intelligently route the non bedrock models to the default model invocation

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [May 19, 2026, 4:50pm UTC](https://forum.cursor.com/t/when-aws-bedrock-is-enabled-fallback-non-bedrock-models-to-default-invocation/161035/6 "2026-05-19T16:50:33Z")

</div>

Thanks for the feedback. This behavior is currently intentional: when AWS Bedrock is enabled, Cursor routes supported requests through your Bedrock configuration rather than automatically falling back to Cursor’s default model invocation for models that aren’t available through Bedrock.

That keeps provider behavior predictable for teams that have intentionally configured Bedrock. However, I understand your point and it’s good feedback.

---

<div class="post-metadata">

**Author:** ![XavierHarkonnen2026](https://avatars.discourse-cdn.com/v4/letter/x/f6c823/32.png) [@XavierHarkonnen2026](https://forum.cursor.com/u/XavierHarkonnen2026)\
**Post date:** [May 19, 2026, 4:55pm UTC](https://forum.cursor.com/t/when-aws-bedrock-is-enabled-fallback-non-bedrock-models-to-default-invocation/161035/8 "2026-05-19T16:55:18Z")

</div>

how annoying would it be to give us a setting to choose to fallback to default?

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [May 19, 2026, 5:09pm UTC](https://forum.cursor.com/t/when-aws-bedrock-is-enabled-fallback-non-bedrock-models-to-default-invocation/161035/9 "2026-05-19T17:09:49Z")

</div>

I understand your frustration but this isn’t something we’re able to change at this time.

For now, the expected path is to disable Bedrock when you want to use Cursor’s default model invocation. We want to keep the behavior explicit rather than introduce a fallback mode that could be surprising.

---

<div class="post-metadata">

**Author:** ![jleben](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jleben/32/117174_2.png) [@jleben](https://forum.cursor.com/u/jleben)\
**Post date:** [August 10, 2026, 9:47pm UTC](https://forum.cursor.com/t/when-aws-bedrock-is-enabled-fallback-non-bedrock-models-to-default-invocation/161035/11 "2026-08-10T21:47:54Z")

</div>

Then why not at least hide or make non-selectable the non-bedrock models from the drop-down box in Chat, making it explicit that they are not available, instead of causing a cryptic API error from Bedrock?