Problem or Use Case

Bedrock is only accessible via OpenRouter, which adds:

• Extra latency (request hops through a middleman)
• ~5–20% cost markup
• No ability to use your own AWS credentials/account
• Loss of enterprise features (VPC endpoints, CloudTrail, negotiated pricing)

Reference Implementation

• OpenClaw supports this today: https://docs.openclaw.ai/providers/bedrock

Proposed Solution

Direct Bedrock integration using the AWS SDK credential chain.

Config Structure

{
  "providers": {
    "amazon-bedrock": {
      "baseUrl": "https://bedrock-runtime.us-east-1.amazonaws.com",
      "api": "bedrock-converse-stream",
      "auth": "aws-sdk"
    }
  }
}

Authentication (Standard AWS SDK Chain)

Option 1: Environment Variables

export AWS_ACCESS_KEY_ID="AKIA..."
export AWS_SECRET_ACCESS_KEY="..."
export AWS_REGION="us-east-1"

Option 2: Shared Credentials

• ~/.aws/credentials

Option 3: IAM Instance Role

• EC2 / ECS role-based authentication

Option 4: Named Profile

export AWS_PROFILE="your-profile-name"

Model ID Format

amazon-bedrock/us.anthropic.claude-sonnet-4-6-v1:0
amazon-bedrock/global.anthropic.claude-opus-4-5-v1:0

Reference:

• OpenClaw's implementation uses bedrock-converse-stream API via @pi-ai/bedrock-converse (https://github.com/pi-ai/bedrock-converse)

• I'd like to implement this myself and submit a PR