Bedrock Provider

@namzu/bedrock is the AWS-native provider package for Namzu. It integrates with the Bedrock Converse API and keeps authentication aligned with standard AWS credential resolution.

1. When to Use It

Choose this package when your application already runs inside AWS or when your model access, regions, and credentials need to stay inside Bedrock.

2. When Not to Use It

Choose another provider when:

you want direct Anthropic API semantics rather than Bedrock's Converse layer
you are not in an AWS-oriented environment and do not benefit from IAM and region-aware behavior

3. Install

pnpm add @namzu/sdk @namzu/bedrock

4. Register and Create the Provider

import { ProviderRegistry } from '@namzu/sdk'
import { registerBedrock } from '@namzu/bedrock'
 
registerBedrock()
 
const { provider, capabilities } = ProviderRegistry.create({
  type: 'bedrock',
  region: 'us-east-1',
  accessKeyId: process.env.AWS_ACCESS_KEY_ID,
  secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
  sessionToken: process.env.AWS_SESSION_TOKEN,
})

5. Sanity-Check With a Direct Provider Call

const response = await provider.chat({
  model: 'anthropic.claude-sonnet-4-20250514',
  messages: [{ role: 'user', content: 'Say hello in one sentence.' }],
})
 
console.log(response.message.content)

6. Use It With a Reactive Agent

import {
  ReactiveAgent,
  ToolRegistry,
  generateProjectId,
  generateSessionId,
  generateTenantId,
} from '@namzu/sdk'
 
const agent = new ReactiveAgent({
  id: 'bedrock-agent',
  name: 'Bedrock Agent',
  version: '1.0.0',
  category: 'docs',
  description: 'Provider documentation example.',
})
 
const result = await agent.run(
  {
    messages: [{ role: 'user', content: 'Say hello.' }],
    workingDirectory: process.cwd(),
  },
  {
    provider,
    tools: new ToolRegistry(),
    model: 'anthropic.claude-sonnet-4-20250514',
    tokenBudget: 8_192,
    timeoutMs: 60_000,
    projectId: generateProjectId(),
    sessionId: generateSessionId(),
    tenantId: generateTenantId(),
  },
)

7. Configuration

Field	Required	Description
`region`	No	AWS region; can also come from the environment or AWS config
`accessKeyId`	No	Explicit AWS access key
`secretAccessKey`	No	Explicit AWS secret key
`sessionToken`	No	Optional AWS session token
`timeout`	No	Request timeout in milliseconds

8. Capability Snapshot

The package exports BEDROCK_CAPABILITIES:

{
  supportsTools: true,
  supportsStreaming: true,
  supportsFunctionCalling: true,
}

9. Operational Notes

If you do not pass explicit credentials, the AWS SDK default credential chain is used.
Model access in Bedrock is region-specific, so enable the models you need in the target AWS region before testing.
The provider also implements listModels() and healthCheck().
Bedrock model identifiers differ from direct vendor identifiers, so keep your runtime model config Bedrock-specific.

10. Common Errors

Error	Meaning	Fix
`Unsupported provider type: bedrock`	registration never happened	call `registerBedrock()` first
auth failures	AWS credentials were not resolved	pass explicit credentials or fix the AWS default chain
model unavailable in region	Bedrock access is not enabled in that region	enable the model in Bedrock and use the correct region

On this page