[FEATURE] Support for AWS BEARER TOKEN BEDROCK #966
Description
📚 Documentation Check
Have you checked if this feature already exists? See our Features Overview or browse all documentation.
Feature Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
supporting AWS_BEARER_TOKEN_BEDROCK makes it easier to call the model without having the AWS ACCESS KEY ID and AWS SECRET ACCESS KEY to be set
Describe the solution you'd like:
A clear and concise description of what you want to happen.
Support usage of AWS_BEARER_TOKEN_BEDROCK instead
Use Case
How would this feature be used?
Describe the specific use case and workflow where this feature would be helpful.
Would allow users to access bedrock models the same way they are now but without having to declare their aws cred/setting profile
Who would benefit from this feature?
- All users
- Users with local LLMs
- Users with cloud LLMs
- Users with MCP servers
- Users with RAG enabled
- Other: [please specify]
Alternatives Considered
Describe alternatives you've considered:
A clear and concise description of any alternative solutions or features you've considered.
Additional Context
Add any other context, screenshots, mockups, or examples about the feature request here.
Implementation Ideas (optional)
If you have technical suggestions for how this could be implemented, share them here.
Related Issues
Link to any related issues or discussions.