AWS Bedrock
Use AWS Bedrock to access a broad catalog of foundation models — Mistral, Amazon Nova, Meta Llama, Cohere, AI21, and more — through RadarOS’s unifiedModelProvider interface. All models are accessed via the Bedrock Converse API.
For Claude models on Bedrock, use the dedicated
awsClaude() provider instead. It uses the native Anthropic SDK for full Claude feature support (extended thinking, document input, etc.).Setup
- Install
- Environment
Install the AWS Bedrock Runtime SDK:
Factory
The Bedrock model identifier. Find model IDs in the AWS Bedrock model catalog.
Optional configuration. See Config below.
Supported Models
| Model ID | Provider | Description |
|---|---|---|
mistral.mistral-large-2402-v1:0 | Mistral | Strong general-purpose performance |
mistral.mistral-small-2402-v1:0 | Mistral | Fast, cost-effective |
amazon.nova-pro-v1:0 | Amazon | General-purpose Nova model |
amazon.nova-lite-v1:0 | Amazon | Lightweight, low-latency |
amazon.nova-micro-v1:0 | Amazon | Ultra-fast, cost-optimized |
meta.llama3-1-70b-instruct-v1:0 | Meta | Llama 3.1 70B Instruct |
meta.llama3-1-8b-instruct-v1:0 | Meta | Llama 3.1 8B Instruct |
cohere.command-r-plus-v1:0 | Cohere | Strong RAG and tool use |
cohere.command-r-v1:0 | Cohere | Fast, efficient |
Using other Bedrock models
Using other Bedrock models
Pass any valid Bedrock model ID to the factory. Manage model access in the AWS Bedrock console. Not all models support all features — check supported features per model.
Config
AWS access key ID. Falls back to
AWS_ACCESS_KEY_ID env var, then default credential chain.AWS secret access key. Falls back to
AWS_SECRET_ACCESS_KEY env var.AWS region. Falls back to
AWS_REGION env var.AWS session token for temporary credentials (STS, SSO). Falls back to
AWS_SESSION_TOKEN env var.Authentication Methods
Method 1: Access Key + Secret (Explicit)
Method 2: Environment Variables (Recommended)
Method 3: Default Credential Chain (SSO, IAM Roles)
If running on EC2, ECS, Lambda, or usingaws sso login, credentials are resolved automatically via the AWS SDK’s default credential provider chain:
Method 4: Temporary Credentials (STS)
Tool Calling
Tool calling is supported via the Bedrock Converse API. Define tools withdefineTool and they work automatically:
Multi-Modal Support
The Bedrock Converse API supports images and documents for models that have vision capabilities (e.g., Amazon Nova).Images
Documents
Full Example
AWS Bedrock vs Direct API
| Feature | Direct API (openai(), anthropic()) | awsBedrock() |
|---|---|---|
| Auth | Provider API key | AWS IAM / credentials |
| Billing | Provider billing | AWS billing (consolidated) |
| VPC / Private | No | Yes (PrivateLink) |
| Model variety | Single provider | Multi-provider catalog |
| Claude support | Full (thinking, docs) | Use awsClaude() instead |
| Compliance | Provider-dependent | SOC2, HIPAA, FedRAMP |
Environment Variables
| Variable | Description |
|---|---|
AWS_ACCESS_KEY_ID | AWS access key ID |
AWS_SECRET_ACCESS_KEY | AWS secret access key |
AWS_REGION | AWS region (default: us-east-1) |
AWS_SESSION_TOKEN | Temporary session token (STS/SSO) |
Cross-References
- AWS Claude — Claude models on Bedrock with full Anthropic feature support
- Custom Provider — Build your own provider for any LLM
- Cost Tracking — Add custom pricing for Bedrock models