Loading...
  • Messages
  • Managed Agents
  • Admin
Search...
⌘K
First steps
Intro to ClaudeQuickstart
Building with Claude
Features overviewUsing the Messages APIHandling stop reasons
Model capabilities
Extended thinkingAdaptive thinkingEffortTask budgets (beta)Fast mode (beta: research preview)Structured outputsCitationsStreaming MessagesBatch processingSearch resultsStreaming refusalsMultilingual supportEmbeddings
Tools
OverviewHow tool use worksTutorial: Build a tool-using agentDefine toolsHandle tool callsParallel tool useTool Runner (SDK)Strict tool useTool use with prompt cachingServer toolsTroubleshootingWeb search toolWeb fetch toolCode execution toolAdvisor toolMemory toolBash toolComputer use toolText editor tool
Tool infrastructure
Tool referenceManage tool contextTool combinationsTool searchProgrammatic tool callingFine-grained tool streaming
Context management
Context windowsCompactionContext editingPrompt cachingCache diagnostics (beta)Token counting
Working with files
Files APIPDF supportImages and vision
Skills
OverviewQuickstartBest practicesSkills for enterpriseSkills in the API
MCP
Remote MCP serversMCP connector
Claude on cloud platforms
Amazon BedrockAmazon Bedrock (legacy)Claude Platform on AWSMicrosoft FoundryVertex AI
Log in
Amazon Bedrock
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...

Solutions

  • AI agents
  • Code modernization
  • Coding
  • Customer support
  • Education
  • Financial services
  • Government
  • Life sciences

Partners

  • Amazon Bedrock
  • Google Cloud's Vertex AI

Learn

  • Blog
  • Courses
  • Use cases
  • Connectors
  • Customer stories
  • Engineering at Anthropic
  • Events
  • Powered by Claude
  • Service partners
  • Startups program

Company

  • Anthropic
  • Careers
  • Economic Futures
  • Research
  • News
  • Responsible Scaling Policy
  • Security and compliance
  • Transparency

Learn

  • Blog
  • Courses
  • Use cases
  • Connectors
  • Customer stories
  • Engineering at Anthropic
  • Events
  • Powered by Claude
  • Service partners
  • Startups program

Help and security

  • Availability
  • Status
  • Support
  • Discord

Terms and policies

  • Privacy policy
  • Responsible disclosure policy
  • Terms of service: Commercial
  • Terms of service: Consumer
  • Usage policy
Messages/Claude on cloud platforms

Claude in Amazon Bedrock

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 (legacy). For an Anthropic-operated alternative on AWS with AWS Marketplace billing and typically same-day feature access, see Claude Platform on AWS.

Access

Claude Opus 4.7 and Claude Haiku 4.5 are open to all Amazon Bedrock customers. Claude Mythos Preview requires an invitation; see 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.

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).

You can also use the standard Anthropic client: set base_url to https://bedrock-mantle.{region}.api.aws/anthropic and pass your bearer token as api_key. This path supports bearer-token authentication only. SigV4 signing requires the dedicated client.

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.

ModelModel IDAccess
Claude Opus 4.7anthropic.claude-opus-4-7Open
Claude Haiku 4.5anthropic.claude-haiku-4-5Open
Claude Mythos Previewanthropic.claude-mythos-previewInvitation only (Project Glasswing)

Upgrading to a newer Claude model? In Claude Code, run /claude-api migrate to apply model ID swaps and breaking parameter changes across your codebase. The skill detects which cloud platform your code targets and adjusts model ID formats and feature changes for that platform. See Migrating to a newer Claude model.

Feature support

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

Supported feature highlights

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

Features not supported

  • 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

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 Opus 4.7 and Claude Haiku 4.5. Claude Mythos Preview is regional only and is available in us-east-1.

AWS regionLocationEndpoint types
af-south-1Africa (Cape Town)Global
ap-northeast-1Asia Pacific (Tokyo)Global, JP, In-region only
ap-northeast-2Asia Pacific (Seoul)Global
ap-northeast-3Asia Pacific (Osaka)Global, JP
ap-south-1Asia Pacific (Mumbai)Global
ap-south-2Asia Pacific (Hyderabad)Global
ap-southeast-1Asia Pacific (Singapore)Global
ap-southeast-2Asia Pacific (Sydney)Global, AU
ap-southeast-3Asia Pacific (Jakarta)Global
ap-southeast-4Asia Pacific (Melbourne)Global, AU, In-region only
ca-central-1Canada (Central)Global, US
ca-west-1Canada West (Calgary)Global
eu-central-1Europe (Frankfurt)Global, EU
eu-central-2Europe (Zurich)Global, EU
eu-north-1Europe (Stockholm)Global, EU, In-region only
eu-south-1Europe (Milan)Global, EU
eu-south-2Europe (Spain)Global, EU
eu-west-1Europe (Ireland)Global, EU, In-region only
eu-west-2Europe (London)Global, EU
eu-west-3Europe (Paris)Global, EU
il-central-1Israel (Tel Aviv)Global
me-central-1Middle East (UAE)Global
sa-east-1South America (São Paulo)Global
us-east-1US East (N. Virginia)Global, US, In-region only
us-east-2US East (Ohio)Global, US, In-region only
us-west-1US West (N. California)Global, US
us-west-2US West (Oregon)Global, US, In-region only

Quotas

Default quota is 2 million input tokens per minute (TPM). You can request up to 4 million input 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 [email protected]. 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.

Was this page helpful?

  • Access
  • Prerequisites
  • Authentication
  • Bedrock service role (recommended)
  • IAM assumed roles
  • Bearer tokens
  • Install an SDK
  • Making your first request
  • Supported models
  • Feature support
  • Supported feature highlights
  • Features not supported
  • Regions
  • Quotas
  • Data retention
  • Monitoring and logging
  • Support