AWS Bedrock

Use your existing AWS infrastructure and enterprise agreements to access Claude. Your API calls route through your VPC, governed by your security policies.

What You Get

Consolidated billing under your AWS account
Compliance with infrastructure your security team has already approved
No new vendor relationships or procurement cycles
Extended context windows up to 1M tokens on supported models

What You Can Do

Access Claude 3.5 Sonnet, Haiku, and Opus models
Use your existing AWS IAM policies for access control
Route requests through your VPC endpoints
Track usage in AWS Cost Explorer alongside other services

Prerequisites

AWS account with Bedrock access enabled
IAM credentials (access key + secret) with Bedrock permissions
Claude models enabled in your Bedrock console

Required IAM Permissions

Your IAM user or role needs these permissions:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "bedrock:InvokeModel",
        "bedrock:InvokeModelWithResponseStream"
      ],
      "Resource": "arn:aws:bedrock:*::foundation-model/anthropic.*"
    }
  ]
}

Setup

Navigate to Settings → General → API Configuration
Select AWS Bedrock as your provider
Enter your AWS credentials:
- Access Key ID
- Secret Access Key
- Region (e.g., us-east-1)
Click Test Connection
Save your configuration

Example Uses

Once configured, Sasha uses Bedrock automatically for all conversations:

"Analyze this quarterly report and summarize the key findings"

"Review this code for security vulnerabilities"

"Help me draft a response to this customer inquiry"

Cost Management

Monitor usage through:

AWS Cost Explorer - Filter by Bedrock service
AWS Budgets - Set alerts for Bedrock spending
Sasha Reports - View token usage by user and session

Troubleshooting

Issue	Solution
"Access denied"	Verify IAM permissions include `bedrock:InvokeModel`
"Model not available"	Enable Claude models in your Bedrock console
"Region not supported"	Try `us-east-1` or `us-west-2`