Claude in Amazon Bedrock (Opus 4.7 and later)

This guide walks you through setting up and making API calls to Claude in Amazon Bedrock. Claude in Amazon Bedrock runs on AWS-managed infrastructure with zero operator access (Anthropic personnel have no access to the inference infrastructure), letting you build sensitive applications entirely inside the AWS security boundary while using the same Messages API shape you use with Anthropic's first-party API.

Access

Amazon Bedrock sets access criteria for each Claude model individually. Claude Fable 5.1, Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5, Claude Opus 4.7, and Claude Haiku 4.5 are open to all Amazon Bedrock customers. For any other model's current criteria, check Amazon Bedrock model access in the AWS console. Claude Mythos Preview requires an invitation through Project Glasswing. For region availability, see Regions.

Prerequisites

Before you begin, ensure you have:

• An AWS account with Amazon Bedrock model access enabled for the Claude models you intend to use.
• The AWS CLI installed and configured (optional, for credential management).

Claude Mythos Preview additionally requires a dedicated AWS account that has been allowlisted by the Bedrock Marketplace team. Your Anthropic account executive can submit your account ID for allowlisting (typically processed within 24 hours), and AWS sends a welcome email once it's complete.

Authentication

Claude in Amazon Bedrock supports three authentication paths. Choose the one that best fits your security requirements.

Bedrock service role (recommended)

Use a Bedrock service role with AWS-managed keys for the most secure, long-lived access:

1. 1

   Admin: provision the service role

   An AWS administrator provisions a Bedrock service role and grants developers iam:PassRole permission on the service role ARN.

2. 2

   Developer: pass the role

   When calling the API, Bedrock assumes the service role on your behalf. See the Amazon Bedrock documentation for how to associate the role with your requests.

IAM assumed roles

For identity-federated access with a 12-hour maximum session:

1. 1

   Admin: configure the IAM role

   Create an IAM role scoped to your Claude models. The trust policy names your identity provider (SAML, OIDC, or AWS Identity Center). The permissions policy grants bedrock-mantle:CreateInference only on the allowed model ARNs.

2. 2

   Developer: authenticate and assume

   Authenticate through your corporate identity provider, then assume the IAM role. AWS STS issues temporary credentials that the SDK or CLI uses to sign requests.

Bearer tokens

For short-term access without IAM roles (12-hour maximum, least preferred):

1. 1

   Admin: restrict token types

   Block long-term keys by attaching a policy that denies bedrock:CallWithBearerToken unless the bedrock:BearerTokenType condition matches a short-term token.

2. 2

   Developer: mint a token

   Use the aws-bedrock-token-generator CLI to mint a bearer token. Pass it in the x-api-key header on each request.

Install an SDK

Anthropic's client SDKs support Claude in Amazon Bedrock through a Bedrock-specific package or module.

pip install -U "anthropic[bedrock]"

Making your first request

The endpoint follows the pattern https://bedrock-mantle.{region}.api.aws/anthropic/v1/messages. Unlike the InvokeModel-based integration, this endpoint uses standard SSE streaming and the same request body shape as Anthropic's first-party API.

The SDK resolves credentials and region using the standard AWS precedence: constructor arguments, then environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_REGION), then the AWS config file and credential chain (SSO, assumed roles, ECS task role, IMDS).

from anthropic import AnthropicBedrockMantle

client = AnthropicBedrockMantle(aws_region="us-east-1")

message = client.messages.create(
    model="anthropic.claude-opus-5",
    max_tokens=1024,
    messages=[{"role": "user", "content": "Hello, Claude"}],
)

print(next(block.text for block in message.content if block.type == "text"))

Supported models

Model IDs in Claude in Amazon Bedrock carry an anthropic. provider prefix. Model capabilities and behaviors are documented on the Models overview page.

Use Claude Code 2.1.255 or later with Claude Fable 5.1 on Amazon Bedrock; run claude update to upgrade.

Feature support

For the full feature list with Amazon Bedrock availability, see Features overview.

Supported feature highlights

• Messages API (/anthropic/v1/messages)
• Prompt caching
• Thinking
• Tool use, including the Bash tool, Computer use tool, Memory tool, and Text editor tool
• Citations

Features not supported

• Structured outputs
• Input sources (URL sources for images and documents, Files API)
• Server-side tools (code execution, web search, web fetch, advisor)
• Agent infrastructure (Agent Skills, MCP connector, programmatic tool calling)
• API endpoints (Message Batches, Models, Admin, Compliance, Usage and Cost)
• Claude Managed Agents
• Server-side fallback (the fallbacks parameter; use the client-side fallback pattern instead)
• Computer use and browser use toolsets (computer_toolset_20260801 and browser_toolset_20260801 are not currently available on Amazon Bedrock; the beta computer use tool versions remain available)

Regions

Claude in Amazon Bedrock is available in the following AWS regions. Amazon Bedrock offers two endpoint types:

• Global: dynamic routing across all available regions for maximum availability. No pricing premium.
• Regional: the endpoint resolves to the single AWS region you specify, for data-residency requirements. Regional endpoints carry a 10% pricing premium over global endpoints. To route across multiple regions within a geography, use an inference profile (US, EU, JP, or AU). Regions marked In-region only in the table support direct single-region routing without an inference profile.

The global endpoint is available for Claude Fable 5.1, Claude Fable 5, Claude Opus 5, Claude Opus 4.8, Claude Opus 4.7, Claude Sonnet 5, and Claude Haiku 4.5. For Claude Fable 5.1, regional endpoints are currently available in us-east-1 only. Claude Mythos Preview is regional only and is available in us-east-1.

Quotas

Default quota is 2 million input tokens per minute (TPM). You can request up to 5 million input TPM and 500,000 output TPM without additional Anthropic approval. AWS enforces requests-per-minute (RPM) limits on the Bedrock side; contact AWS support for RPM adjustments.

Data retention

Data handling for this offering is governed by Amazon Bedrock. For details, see Data protection in Amazon Bedrock.

Monitoring and logging

Claude in Amazon Bedrock emits logs to both CloudWatch and CloudTrail. Anthropic recommends retaining activity logs on at least a 30-day rolling basis to understand usage patterns and investigate potential issues.

Support

For support, contact bedrock-ant-eap@amazon.com. Include your AWS account ID and the request-id from any failed API responses.