feat(bedrock): config options and authentication precedence #6377
+220
−124
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 configuration file support for Amazon Bedrock provider with
profile,region, andendpointoptions. Documents authentication precedence to clarify that bearer tokens take priority over AWS credential chain methods.Changes
Provider Configuration (
provider.ts)profile,region, andendpointoptions inopencode.jsonfromNodeProviderChain()for proper credential resolutionTests (
amazon-bedrock.test.ts)Documentation (
config.mdx,providers.mdx)AWS_BEARER_TOKEN_BEDROCKor/connect) take precedence over credential chainCLI (
auth.ts)/connect amazon-bedrockhelp message to show clear credential priority orderConfiguration Example
{ "provider": { "amazon-bedrock": { "options": { "region": "us-east-1", "profile": "my-aws-profile", "endpoint": "https://bedrock-runtime.us-east-1.vpce-xxxxx.amazonaws.com" } } } }Authentication Precedence
AWS_BEARER_TOKEN_BEDROCKor/connect)Notes: