Files

Alex Fallah 8effb557d5 feat: add dynamic Bedrock model discovery

Add automatic discovery of AWS Bedrock models using ListFoundationModels API.
When AWS credentials are detected, models that support streaming and text output
are automatically discovered and made available.

- Add @aws-sdk/client-bedrock dependency
- Add discoverBedrockModels() with caching (default 1 hour)
- Add resolveImplicitBedrockProvider() for auto-registration
- Add BedrockDiscoveryConfig for optional filtering by provider/region
- Filter to active, streaming, text-output models only
- Update docs/bedrock.md with auto-discovery documentation

2026-01-24 01:15:06 +00:00

3.1 KiB

Raw Blame History

summary, read_when

summary

read_when

Use Amazon Bedrock (Converse API) models with Clawdbot

You want to use Amazon Bedrock models with Clawdbot

You need AWS credential/region setup for model calls

Amazon Bedrock

Clawdbot can use Amazon Bedrock models via pi‑ai’s Bedrock Converse streaming provider. Bedrock auth uses the AWS SDK default credential chain, not an API key.

What pi‑ai supports

Provider: amazon-bedrock
API: bedrock-converse-stream
Auth: AWS credentials (env vars, shared config, or instance role)
Region: AWS_REGION or AWS_DEFAULT_REGION (default: us-east-1)

Automatic model discovery

If AWS credentials are detected, Clawdbot can automatically discover Bedrock models that support streaming and text output. Discovery uses bedrock:ListFoundationModels and is cached (default: 1 hour).

Config options live under models.bedrockDiscovery:

{
  models: {
    bedrockDiscovery: {
      enabled: true,
      region: "us-east-1",
      providerFilter: ["anthropic", "amazon"],
      refreshInterval: 3600
    }
  }
}

Notes:

enabled defaults to true when AWS credentials are present.
region defaults to AWS_REGION or AWS_DEFAULT_REGION, then us-east-1.
providerFilter matches Bedrock provider names (for example anthropic).
refreshInterval is seconds; set to 0 to disable caching.

Setup (manual)

Ensure AWS credentials are available on the gateway host:

export AWS_ACCESS_KEY_ID="AKIA..."
export AWS_SECRET_ACCESS_KEY="..."
export AWS_REGION="us-east-1"
# Optional:
export AWS_SESSION_TOKEN="..."
export AWS_PROFILE="your-profile"
# Optional (Bedrock API key/bearer token):
export AWS_BEARER_TOKEN_BEDROCK="..."

Add a Bedrock provider and model to your config (no apiKey required):

{
  models: {
    providers: {
      "amazon-bedrock": {
        baseUrl: "https://bedrock-runtime.us-east-1.amazonaws.com",
        api: "bedrock-converse-stream",
        auth: "aws-sdk",
        models: [
          {
            id: "anthropic.claude-3-7-sonnet-20250219-v1:0",
            name: "Claude 3.7 Sonnet (Bedrock)",
            reasoning: true,
            input: ["text"],
            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
            contextWindow: 200000,
            maxTokens: 8192
          }
        ]
      }
    }
  },
  agents: {
    defaults: {
      model: { primary: "amazon-bedrock/anthropic.claude-3-7-sonnet-20250219-v1:0" }
    }
  }
}

Notes

Bedrock requires model access enabled in your AWS account/region.
Automatic discovery needs the bedrock:ListFoundationModels permission.
If you use profiles, set AWS_PROFILE on the gateway host.
Clawdbot surfaces the credential source in this order: AWS_BEARER_TOKEN_BEDROCK, then AWS_ACCESS_KEY_ID + AWS_SECRET_ACCESS_KEY, then AWS_PROFILE, then the default AWS SDK chain.
Reasoning support depends on the model; check the Bedrock model card for current capabilities.
If you prefer a managed key flow, you can also place an OpenAI‑compatible proxy in front of Bedrock and configure it as an OpenAI provider instead.

3.1 KiB Raw Blame History Unescape Escape