AWS Bedrock

AWS Bedrock is Amazon’s managed inference platform. It hosts Anthropic’s Claude family, Meta’s Llama, Mistral, and Amazon’s own Nova models — all behind a unified Bedrock Runtime API. Use this vendor when your organization is AWS-heavy or needs the BAA / data-residency story Bedrock provides.

Get credentials

Bedrock supports two auth modes. Pick based on what your organization already uses.

Option A — API Key (newer, simpler)

1. Sign in to the AWS Console, go to Amazon Bedrock.
2. Open API keys in the sidebar.
3. Click Generate API key, copy the bearer token.

This is the easiest path — one secret, no IAM dance.

Option B — IAM credentials (legacy, more flexible)

If your organization issues IAM credentials per-team or per-environment:

1. Create an IAM user (or use an existing one) with the policy AmazonBedrockFullAccess (or a tighter custom policy that grants bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream).
2. From IAM → Security credentials → Create access key, save the Access Key ID and Secret Access Key.
3. If you’re using STS / temporary credentials, you’ll also have a Session Token.

Configure in jambonz

In the portal: Account → LLM Services → + Add LLM Service → AWS Bedrock.

The form lets you pick API Key or IAM Credentials auth.

API Key fields

IAM fields

Click Test to verify. The probe issues ListFoundationModels against the control plane.

Use in an agent verb

1
session.agent({
2
  llm: {
3
    vendor: 'bedrock',
4
    model: 'us.anthropic.claude-haiku-4-5-20251001-v1:0',
5
    llmOptions: {
6
      systemPrompt: 'You are a helpful voice assistant.',
7
    },
8
  },
9
  stt: { vendor: 'deepgram', language: 'en-US' },
10
  tts: { vendor: 'cartesia', voice: 'sonic-english' },
11
  turnDetection: 'krisp',
12
  bargeIn: { enable: true },
13
  actionHook: '/agent-complete',
14
}).send();

Available Models

See AWS’s Bedrock model cards for the authoritative current list — each card has model id, supported regions, modalities, and pricing. Common picks:

Quirks & errors