Creor/Docs
Dashboard

AWS Bedrock

AWS Bedrock lets you access Claude, Llama, Mistral, Amazon Nova, and DeepSeek models through your existing AWS infrastructure. All traffic stays within AWS, making it ideal for organizations with strict compliance requirements.

Available Models

AWS Bedrock hosts models from multiple providers. Available models depend on your AWS region and account access.

Model FamilyExample Model IDsProvider
Claude 4 Sonnetanthropic.claude-sonnet-4-20250514-v1:0Anthropic
Claude 4 Opusanthropic.claude-opus-4-20250514-v1:0Anthropic
Claude 3.5 Haikuanthropic.claude-3-5-haiku-20241022-v1:0Anthropic
Llama 3.xmeta.llama3-70b-instruct-v1:0Meta
Mistral Largemistral.mistral-large-2407-v1:0Mistral
Amazon Nova Proamazon.nova-pro-v1:0Amazon
Amazon Nova Liteamazon.nova-lite-v1:0Amazon
Amazon Nova Microamazon.nova-micro-v1:0Amazon
DeepSeekdeepseek.deepseek-r1-v1:0DeepSeek

Note

You must request access to models in the AWS Bedrock console before they can be used. Go to the Bedrock console, select "Model access" in the sidebar, and enable the models you need.

Setup

Prerequisites

  • An AWS account with Bedrock access enabled.
  • IAM credentials with bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream permissions.
  • The desired models enabled in your Bedrock console for your region.

Step 1: Configure AWS Credentials

The simplest approach is to use the AWS CLI to configure your credentials:

aws configure

Or set environment variables directly:

1
2
3
export AWS_ACCESS_KEY_ID="your-access-key"
export AWS_SECRET_ACCESS_KEY="your-secret-key"
export AWS_REGION="us-east-1"

Step 2: Verify Access

Once credentials are configured, Creor auto-detects the Bedrock provider. No additional setup is needed in Creor.

Configuration

Set a Bedrock model as your default in creor.json:

1
2
3
{
"model": "amazon-bedrock/anthropic.claude-sonnet-4-20250514-v1:0"
}

Use different Bedrock models for different agents:

1
2
3
4
5
6
7
8
9
10
11
12
13
{
"agent": {
"build": {
"model": "amazon-bedrock/anthropic.claude-sonnet-4-20250514-v1:0"
},
"plan": {
"model": "amazon-bedrock/anthropic.claude-opus-4-20250514-v1:0"
},
"explore": {
"model": "amazon-bedrock/amazon.nova-lite-v1:0"
}
}
}

Region and Cross-Region Inference

Bedrock automatically applies cross-region inference prefixes based on your configured AWS region. For example, if you are in us-east-1, Claude models are automatically prefixed with us. for cross-region inference.

Region PrefixAWS RegionsExample
us.us-east-1, us-west-2, etc.us.anthropic.claude-sonnet-4-20250514-v1:0
eu.eu-west-1, eu-central-1, etc.eu.anthropic.claude-sonnet-4-20250514-v1:0
jp.ap-northeast-1jp.anthropic.claude-sonnet-4-20250514-v1:0
apac.ap-southeast-1, ap-south-1, etc.apac.anthropic.claude-sonnet-4-20250514-v1:0
au.ap-southeast-2, ap-southeast-4au.anthropic.claude-sonnet-4-20250514-v1:0

You can also manually specify a cross-region prefix in the model ID (e.g., global.anthropic.claude-sonnet-4-20250514-v1:0) and Creor will use it as-is without adding another prefix.

Authentication Methods

Creor supports multiple AWS authentication methods, resolved in this order:

1. AWS Bearer Token

Set via environment variable or the Creor Settings UI:

export AWS_BEARER_TOKEN_BEDROCK="your-bearer-token"

2. AWS Credential Chain

If no bearer token is set, Creor uses the standard AWS credential provider chain:

  • Environment variables (AWS_ACCESS_KEY_ID + AWS_SECRET_ACCESS_KEY)
  • Named AWS profile (via AWS_PROFILE or creor.json config)
  • Web identity token (AWS_WEB_IDENTITY_TOKEN_FILE for EKS/IRSA)
  • Instance metadata (EC2 instance roles)

3. Named Profile

Use a specific AWS profile from ~/.aws/credentials:

1
2
3
4
5
6
7
8
9
10
{
"provider": {
"amazon-bedrock": {
"options": {
"profile": "my-bedrock-profile",
"region": "us-west-2"
}
}
}
}

Advanced Options

Custom Endpoint

For VPC endpoints or custom Bedrock endpoints:

1
2
3
4
5
6
7
8
9
10
{
"provider": {
"amazon-bedrock": {
"options": {
"endpoint": "https://vpce-xxx.bedrock-runtime.us-east-1.vpce.amazonaws.com",
"region": "us-east-1"
}
}
}
}

Region Override

Override the region at the provider level (takes precedence over the AWS_REGION environment variable):

1
2
3
4
5
6
7
8
9
{
"provider": {
"amazon-bedrock": {
"options": {
"region": "eu-west-1"
}
}
}
}

Best For

  • Organizations that must keep all traffic within AWS infrastructure.
  • Teams using AWS IAM for access control and audit logging.
  • Deployments requiring VPC endpoints for network isolation.
  • Multi-model strategies using Claude, Llama, and Nova through a single provider.
  • Compliance-driven environments (SOC 2, HIPAA, FedRAMP).

Anthropic (Direct)

Use Claude models directly through Anthropic's API.

Azure OpenAI

Run GPT models on Azure infrastructure.

PreviousGoogleModels & ProvidersNextAzure OpenAIModels & Providers