feat: add Amazon Bedrock support with API key authentication #3032
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds Amazon Bedrock as an LLM provider option using the new Bedrock API key authentication feature. This is a simpler approach than traditional AWS credentials (access_key_id, secret_access_key, region).
Changes:
shared.tsxwithapi_keyrequirementamazon_bedrockcase inuseLLMConnection.tsusing@ai-sdk/amazon-bedrockpackageconfigure.tsxpointing to AWS Console for API key generationReview & Testing Checklist for Human
us-east-1. Verify this is acceptable or if it should be user-configurable@ai-sdk/amazon-bedrockpackage'sapiKeyparameter works as expected with Bearer token authTest Plan
Notes
This replaces the more complex AWS credentials approach from PR #3005 with a simpler API key-based authentication.
Link to Devin run: https://app.devin.ai/sessions/6079ce2504d14c4685c5e6832e523fbd
Requested by: @yujonglee