Summary

• Adds Amazon Bedrock provider support across client and server
• Enables model selection for Bedrock (Titan Text Lite, Claude 3.5 Sonnet, Llama 3.3 70B Instruct)
• Implements flexible Bedrock credentials parsing (JSON or pipe-delimited) and region override via AWS_BEDROCK_REGION
• Updates UI with Bedrock provider entry, config guidance, and branding

Changes

Core data/types

• Add bedrock to ModelProvider in shared/types.ts
• Register Bedrock models in SUPPORTED_MODELS (Titan Text Lite, Claude 3.5 Sonnet Bedrock, Llama 3.3 70B Instruct Bedrock)

Backend integration

• server/utils/chat-helpers.ts: add support for provider "bedrock" with:
  • region derived from AWS_BEDROCK_REGION / AWS_REGION / AWS_DEFAULT_REGION (default us-west-2)
  • credentials parsed from API key string as JSON or as pipe-delimited values (accessKeyId|secretAccessKey[|sessionToken])
  • required accessKeyId and secretAccessKey, otherwise throws a descriptive error
  • uses createAmazonBedrock with configured options

Client/UI

• client/public/bedrock_logo.svg: new Bedrock branding asset
• client/src/components/SettingsTab.tsx: add Bedrock as a provider option with logo, description, and credentials placeholder
• client/src/components/chat/chat-helpers.ts: import bedrock logo and map provider to Bedrock logo; Bedrock color mapping added
• client/src/components/chat/mcpjam-model-selector.tsx: map bedrock to display "Amazon Bedrock"
• client/src/components/chat/model-selector.tsx: show Bedrock as a provider with display name
• client/src/components/setting/ProviderConfigDialog.tsx: add guidance for Bedrock credentials (JSON or pipe-delimited) and region variable with defaults
• client/src/hooks/use-ai-provider-keys.ts: extend tokens with bedrock key and default to empty string
• client/src/hooks/use-chat.ts: include bedrock in provider keys (hasToken check)
• client/src/lib/chat-utils.ts: default temperature for bedrock set to 0

Documentation & onboarding

• docs/contributing/onboarding.mdx: update provider list to include Amazon Bedrock; example credential setup mentions BEDROCK_CREDENTIALS and region
• docs/evals/overview.mdx: map bedrock to BEDROCK_CREDENTIALS in providerApiKeys
• docs/inspector/llm-playground.mdx: add Bedrock section and usage notes

Packaging & dependencies

• package.json (client and server): include @ai-sdk/amazon-bedrock as a dependency
• package-lock.json and server/package-lock.json updated accordingly
• server/package.json updated to include the bedrock package

Misc

• README.md: note about Amazon Bedrock support and setup steps

Test plan

• Configure Bedrock provider in Settings → LLM Provider API Keys with credentials in one of: JSON string or AKI/Secret key pair separated by pipes
• Verify Bedrock provider appears in the provider list UI and is selectable in model/config dialogs
• Confirm ProviderConfigDialog presents Bedrock-specific guidance for credentials and region (AWS_BEDROCK_REGION) defaulting to us-west-2
• Open a chat and select an Amazon Bedrock model (Titan Text Lite, Claude 3.5 Sonnet Bedrock, or Llama 3.3 70B Instruct Bedrock) and send a message
• Ensure default temperature handling for Bedrock is 0 via chat-utils
• Validate credentials can be provided as JSON or as a delimited string and that requests are constructed with correct accessKeyId/secretAccessKey (and sessionToken if provided)
• Confirm region overrides via environment variable AWS_BEDROCK_REGION (or AWS_REGION / AWS_DEFAULT_REGION) are respected by the server integration

Notes:

• This PR adds Bedrock support across the UI, client helpers, server backend, types, and docs. If you rely on existing providers, no changes should be required beyond selecting Bedrock in the UI and supplying credentials in the supported formats.

🌿 Generated by Terry

ℹ️ Tag @terragon-labs to ask questions and address PR feedback

📎 Task: https://www.terragonlabs.com/task/addebe1f-a151-42bd-bd36-702d8541203f