--- title: Claude in Amazon Bedrock (Opus 4.7 and later) url: https://platform.claude.com/docs/en/build-with-claude/claude-in-amazon-bedrock description: Access Claude models through Amazon Bedrock with AWS-native authentication, billing, and security boundaries. --- 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. This page covers Claude in Amazon Bedrock, which serves Claude through the Messages API at `/anthropic/v1/messages` on AWS-managed infrastructure. The previous Amazon Bedrock integration (the `InvokeModel` and `Converse` APIs with ARN-versioned model identifiers) remains available and is documented at [Claude on Amazon Bedrock (Opus 4.6 and earlier)](https://platform.claude.com/docs/en/build-with-claude/claude-on-amazon-bedrock-legacy). For an Anthropic-operated alternative on AWS with AWS Marketplace billing and typically same-day feature access, see [Claude Platform on AWS](https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws). ## 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](https://console.aws.amazon.com/bedrock/home#/modelaccess) in the AWS console. Claude Mythos Preview requires an invitation through [Project Glasswing](https://anthropic.com/glasswing). For region availability, see [Regions](https://platform.claude.com/docs/en/build-with-claude/claude-in-amazon-bedrock#regions). ## Prerequisites Before you begin, ensure you have: * An AWS account with [Amazon Bedrock model access](https://console.aws.amazon.com/bedrock/home#/modelaccess) enabled for the Claude models you intend to use. * The [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html) 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: An AWS administrator provisions a Bedrock service role and grants developers `iam:PassRole` permission on the service role ARN. When calling the API, Bedrock assumes the service role on your behalf. See the [Amazon Bedrock documentation](https://docs.aws.amazon.com/bedrock/latest/userguide/bedrock-mantle.html) for how to associate the role with your requests. ### IAM assumed roles For identity-federated access with a 12-hour maximum session: 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. 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): Block long-term keys by attaching a policy that denies `bedrock:CallWithBearerToken` unless the `bedrock:BearerTokenType` condition matches a short-term 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](https://platform.claude.com/docs/en/cli-sdks-libraries/overview) support Claude in Amazon Bedrock through a Bedrock-specific package or module. ```bash pip install -U "anthropic[bedrock]" ``` ```bash npm install @anthropic-ai/bedrock-sdk ``` ```bash dotnet add package Anthropic.Bedrock ``` ```bash go get github.com/anthropics/anthropic-sdk-go/bedrock ``` ```kotlin implementation("com.anthropic:anthropic-java:2.73.0") implementation("com.anthropic:anthropic-java-bedrock:2.73.0") ``` ```xml com.anthropic anthropic-java 2.73.0 com.anthropic anthropic-java-bedrock 2.73.0 ``` ```bash composer require anthropic-ai/sdk aws/aws-sdk-php ``` ```bash # Gemfile gem "anthropic" gem "aws-sdk-core" ``` ## 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). ```bash curl https://bedrock-mantle.us-east-1.api.aws/anthropic/v1/messages \ --aws-sigv4 "aws:amz:us-east-1:bedrock-mantle" \ --user "$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY" \ -H "x-amz-security-token: $AWS_SESSION_TOKEN" \ -H "content-type: application/json" \ -H "anthropic-version: 2023-06-01" \ -d '{ "model": "anthropic.claude-opus-5-5", "max_tokens": 1024, "messages": [ {"role": "user", "content": "Hello, Claude"} ] }' ``` The `ant` CLI does not support Amazon Bedrock. Use either cURL or an SDK. ```python from anthropic import AnthropicBedrockMantle client = AnthropicBedrockMantle(aws_region="us-east-1") message = client.messages.create( model="anthropic.claude-opus-5-5", max_tokens=1024, messages=[{"role": "user", "content": "Hello, Claude"}], ) print(next(block.text for block in message.content if block.type == "text")) ``` ```typescript import { AnthropicBedrockMantle } from "@anthropic-ai/bedrock-sdk"; const client = new AnthropicBedrockMantle({ awsRegion: "us-east-1" }); const message = await client.messages.create({ model: "anthropic.claude-opus-5-5", max_tokens: 1024, messages: [{ role: "user", content: "Hello, Claude" }] }); const textBlock = message.content.find((block) => block.type === "text"); if (textBlock) { console.log(textBlock.text); } ``` ```csharp using Anthropic.Bedrock; using Anthropic.Models.Messages; var client = new AnthropicBedrockMantleClient(new() { AwsRegion = "us-east-1" }); var message = await client.Messages.Create(new() { Model = "anthropic.claude-opus-5-5", MaxTokens = 1024, Messages = [new() { Role = Role.User, Content = "Hello, Claude" }], }); foreach (var item in message.Content) { if (item.Value is TextBlock block) { Console.WriteLine(block.Text); break; } } ``` ```go client, err := bedrock.NewMantleClient(context.Background(), bedrock.MantleClientConfig{ AWSRegion: "us-east-1", }) if err != nil { panic(err) } message, err := client.Messages.New(context.Background(), anthropic.MessageNewParams{ Model: "anthropic.claude-opus-5-5", MaxTokens: 1024, Messages: []anthropic.MessageParam{ anthropic.NewUserMessage(anthropic.NewTextBlock("Hello, Claude")), }, }) if err != nil { panic(err) } for _, block := range message.Content { if textBlock, ok := block.AsAny().(anthropic.TextBlock); ok { fmt.Println(textBlock.Text) break } } ``` ```java import com.anthropic.bedrock.backends.BedrockMantleBackend; import com.anthropic.client.AnthropicClient; import com.anthropic.client.okhttp.AnthropicOkHttpClient; import com.anthropic.models.messages.ContentBlock; import com.anthropic.models.messages.Message; import com.anthropic.models.messages.MessageCreateParams; void main() { AnthropicClient client = AnthropicOkHttpClient.builder() .backend(BedrockMantleBackend.fromEnv()) .build(); Message message = client.messages().create( MessageCreateParams.builder() .model("anthropic.claude-opus-5-5") .maxTokens(1024) .addUserMessage("Hello, Claude") .build() ); message.content().stream() .filter(ContentBlock::isText) .findFirst() .ifPresent(block -> IO.println(block.asText().text())); } ``` ```php use Anthropic\Bedrock\MantleClient; $client = new MantleClient(awsRegion: 'us-east-1'); $message = $client->messages->create( model: 'anthropic.claude-opus-5-5', maxTokens: 1024, messages: [ ['role' => 'user', 'content' => 'Hello, Claude'], ], ); echo array_find($message->content, fn ($block) => $block->type === 'text')->text; ``` ```ruby require "anthropic" client = Anthropic::BedrockMantleClient.new(aws_region: "us-east-1") message = client.messages.create( model: "anthropic.claude-opus-5-5", max_tokens: 1024, messages: [{role: "user", content: "Hello, Claude"}] ) puts message.content.find { it.type == :text }.text ``` You can also create the standard client with `Anthropic` (go: `anthropic.NewClient()`; java: `AnthropicOkHttpClient.builder()`; csharp: `AnthropicClient`; php: `Anthropic\Client`; ruby: `Anthropic::Client`): set `base_url` (typescript: `baseURL`; go: `option.WithBaseURL()`; java: `.baseUrl()`; csharp: `BaseUrl`; php: `baseUrl`) to `https://bedrock-mantle.{region}.api.aws/anthropic` and pass your bearer token as `api_key` (typescript, php: `apiKey`; go: `option.WithAPIKey()`; java: `.apiKey()`; csharp: `ApiKey`). This path supports bearer-token authentication only. SigV4 signing requires `AnthropicBedrockMantle` (csharp: `AnthropicBedrockMantleClient`; go: `bedrock.NewMantleClient`; java: `BedrockMantleBackend`; php: `MantleClient`; ruby: `Anthropic::BedrockMantleClient`). ## Supported models Model IDs in Claude in Amazon Bedrock carry an `anthropic.` provider prefix. Model capabilities and behaviors are documented on the [Models overview](https://platform.claude.com/docs/en/models/overview) page. | Model | Model ID | Access | | :------------------------------------------------------------------------------------------ | :-------------------------------- | :-------------------------------------------------------------------------------------------------- | | Claude Fable 5.1 | `anthropic.claude-fable-5-1` | Open | | Claude Mythos 5.1 ([limited availability](https://support.claude.com/en/articles/14604842)) | `anthropic.claude-mythos-5-1` | Active (verification required) | | Claude Fable 5 | `anthropic.claude-fable-5` | Open | | Claude Mythos 5 ([limited availability](https://support.claude.com/en/articles/14604842)) | `anthropic.claude-mythos-5` | Active (verification required) | | Claude Mythos Preview ([limited availability](https://anthropic.com/glasswing)) | `anthropic.claude-mythos-preview` | Invitation only | | Claude Opus 5.5 | `anthropic.claude-opus-5-5` | [See Access](https://platform.claude.com/docs/en/build-with-claude/claude-in-amazon-bedrock#access) | | Claude Opus 5 | `anthropic.claude-opus-5` | [See Access](https://platform.claude.com/docs/en/build-with-claude/claude-in-amazon-bedrock#access) | | Claude Opus 4.8 | `anthropic.claude-opus-4-8` | Open | | Claude Opus 4.7 | `anthropic.claude-opus-4-7` | Open | | Claude Sonnet 5.5 | `anthropic.claude-sonnet-5-5` | [See Access](https://platform.claude.com/docs/en/build-with-claude/claude-in-amazon-bedrock#access) | | Claude Sonnet 5 | `anthropic.claude-sonnet-5` | Open | | Claude Haiku 5.5 | `anthropic.claude-haiku-5-5` | [See Access](https://platform.claude.com/docs/en/build-with-claude/claude-in-amazon-bedrock#access) | | Claude Haiku 4.5 | `anthropic.claude-haiku-4-5` | Open | Use the latest version of Claude Code with Claude in Amazon Bedrock; run `claude update` to upgrade. Upgrading to a newer Claude model? The [Claude API skill](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/claude-api-skill#migrating-to-a-newer-claude-model) in Claude Code applies model ID swaps and breaking parameter changes across your code base: Let Claude Code migrate your code for you ```text /claude-api migrate this project to the latest Claude Opus model ``` The skill detects which cloud platform your code targets and adjusts model ID formats and feature changes for that platform. ## Feature support For the full feature list with Amazon Bedrock availability, see [Features overview](https://platform.claude.com/docs/en/build-with-claude/overview). ### Supported feature highlights * [Messages API](https://platform.claude.com/docs/en/api/messages/create) (`/anthropic/v1/messages`) * [Prompt caching](https://platform.claude.com/docs/en/build-with-claude/prompt-caching) * [Thinking](https://platform.claude.com/docs/en/build-with-claude/thinking) * [Tool use](https://platform.claude.com/docs/en/agents-and-tools/tool-use/overview), including the [Bash tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/bash-tool), [Computer use tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/computer-use-tool), [Memory tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/memory-tool), and [Text editor tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/text-editor-tool) * [Citations](https://platform.claude.com/docs/en/build-with-claude/citations) ### Features not supported * [Structured outputs](https://platform.claude.com/docs/en/build-with-claude/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](https://platform.claude.com/docs/en/build-with-claude/refusals-and-fallback#server-side-fallback); use the [client-side fallback pattern](https://platform.claude.com/docs/en/build-with-claude/refusals-and-fallback#client-side-fallback) instead) * [Computer use](https://platform.claude.com/docs/en/agents-and-tools/tool-use/computer-use-tool) and [browser use](https://platform.claude.com/docs/en/agents-and-tools/tool-use/browser-use-tool) 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](https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html) (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.5, Claude Opus 5, Claude Opus 4.8, Claude Opus 4.7, Claude Sonnet 5.5, Claude Sonnet 5, Claude Haiku 5.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`. | AWS region | Location | Endpoint types | | ---------------- | ------------------------- | -------------------------- | | `af-south-1` | Africa (Cape Town) | Global | | `ap-northeast-1` | Asia Pacific (Tokyo) | Global, JP, In-region only | | `ap-northeast-2` | Asia Pacific (Seoul) | Global | | `ap-northeast-3` | Asia Pacific (Osaka) | Global, JP | | `ap-south-1` | Asia Pacific (Mumbai) | Global | | `ap-south-2` | Asia Pacific (Hyderabad) | Global | | `ap-southeast-1` | Asia Pacific (Singapore) | Global | | `ap-southeast-2` | Asia Pacific (Sydney) | Global, AU | | `ap-southeast-3` | Asia Pacific (Jakarta) | Global | | `ap-southeast-4` | Asia Pacific (Melbourne) | Global, AU, In-region only | | `ca-central-1` | Canada (Central) | Global, US | | `ca-west-1` | Canada West (Calgary) | Global | | `eu-central-1` | Europe (Frankfurt) | Global, EU | | `eu-central-2` | Europe (Zurich) | Global, EU | | `eu-north-1` | Europe (Stockholm) | Global, EU, In-region only | | `eu-south-1` | Europe (Milan) | Global, EU | | `eu-south-2` | Europe (Spain) | Global, EU | | `eu-west-1` | Europe (Ireland) | Global, EU, In-region only | | `eu-west-2` | Europe (London) | Global, EU | | `eu-west-3` | Europe (Paris) | Global, EU | | `il-central-1` | Israel (Tel Aviv) | Global | | `me-central-1` | Middle East (UAE) | Global | | `sa-east-1` | South America (São Paulo) | Global | | `us-east-1` | US East (N. Virginia) | Global, US, In-region only | | `us-east-2` | US East (Ohio) | Global, US, In-region only | | `us-west-1` | US West (N. California) | Global, US | | `us-west-2` | US West (Oregon) | Global, US, In-region only | ## 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](https://docs.aws.amazon.com/bedrock/latest/userguide/data-protection.html). ## 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](mailto:bedrock-ant-eap@amazon.com)**. Include your AWS account ID and the `request-id` from any failed API responses. **Claude Mythos Preview** is a research preview model available to invited customers on Amazon Bedrock. For more information, see [Project Glasswing](https://anthropic.com/glasswing).