Claude Opus 4.5 - Amazon Bedrock
Services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the AWS European Sovereign Cloud Region, see the AWS European Sovereign Cloud User Guide.

Claude Opus 4.5

Anthropic — Claude Opus 4.5

Model Details

Claude Opus 4.5 is Anthropic's model for coding, agents, and computer use with improvements for spreadsheets and long-running chats. For more information about model development and performance, see the model/service card.

  • Model launch date: Nov 24, 2025

  • Model EOL date: No sooner than 3/25/2026

  • End User License Agreements and Terms of Use: View

  • Model lifecycle: Active

  • Context window: 200K tokens

  • Max output tokens: 64K

  • Reasoning: Supported

  • Knowledge cutoff: Mar 2025

Input Modalities Output Modalities APIs supported Endpoints supported
No AudioNo EmbeddingNo ResponsesYes bedrock-runtime
Yes ImageNo ImageNo Chat CompletionsNo bedrock-mantle
No SpeechNo SpeechYes Invoke
Yes TextYes TextYes Converse
No VideoNo Video

Capabilities and Features

Bedrock Features

Features supported using bedrock-runtime endpoint

Pricing

For pricing, please refer to the Amazon Bedrock Pricing page.

Programmatic Access

Use the following model IDs and endpoint URLs to access this model programmatically. For more information about the available APIs and endpoints, see APIs supported and Endpoints supported.

Endpoint Model ID In-Region endpoint URL Geo inference ID Global inference ID
bedrock-runtime anthropic.claude-opus-4-5-20251101-v1:0 https://bedrock-runtime.{region}.amazonaws.com

us.anthropic.claude-opus-4-5-20251101-v1:0

eu.anthropic.claude-opus-4-5-20251101-v1:0

global.anthropic.claude-opus-4-5-20251101-v1:0

For example, if region is us-east-1 (N. Virginia), then the bedrock-runtime endpoint URL will be "https://bedrock-runtime.us-east-1.amazonaws.com" and for bedrock-mantle will be "https://bedrock-mantle.us-east-1.api.aws/v1".

Service Tiers

Amazon Bedrock offers multiple service tiers to match your workload requirements. Standard provides pay-per-token access with no commitment. Priority offers higher throughput with a time-based commitment. Flex provides lower-cost access for flexible, non-time-sensitive workloads. Reserved provides dedicated throughput with a term commitment for predictable workloads. For more information, see service tiers.

Standard Priority Flex Reserved
Yes No No Yes

Regional Availability

Regional availability at a glance

Bedrock offers three inference options: In-Region keeps requests within a single Region for strict compliance, Geo Cross-Region routes across Regions within a geography (US, EU, etc.) for higher throughput while respecting data residency, and Global Cross-Region routes anywhere worldwide for maximum throughput when there are no residency constraints. Refer to the Regional availability page for more details.

Region In-Region Geo Global
us-east-1 (N. Virginia)NoYesYes
us-east-2 (Ohio)NoYesYes
us-west-1 (N. California)NoYesYes
us-west-2 (Oregon)NoYesYes
ca-central-1 (Canada)NoYesYes
ca-west-1 (Calgary)NoNoYes
eu-central-1 (Frankfurt)NoYesYes
eu-central-2 (Zurich)NoYesYes
eu-north-1 (Stockholm)NoYesYes
eu-south-1 (Milan)NoYesYes
eu-south-2 (Spain)NoYesYes
eu-west-1 (Ireland)NoYesYes
eu-west-2 (London)NoYesYes
eu-west-3 (Paris)NoYesYes
ap-east-2 (Malaysia)NoNoYes
ap-northeast-1 (Tokyo)NoNoYes
ap-northeast-2 (Seoul)NoNoYes
ap-northeast-3 (Osaka)NoNoYes
ap-south-1 (Mumbai)NoNoYes
ap-south-2 (Hyderabad)NoNoYes
ap-southeast-1 (Singapore)NoNoYes
ap-southeast-2 (Sydney)NoNoYes
ap-southeast-3 (Jakarta)NoNoYes
ap-southeast-4 (Melbourne)NoNoYes
ap-southeast-5 (Auckland)NoNoYes
ap-southeast-7 (Kuala Lumpur)NoNoYes
il-central-1 (Tel Aviv)NoNoYes
me-central-1 (UAE)NoNoYes
me-south-1 (Bahrain)NoNoYes
af-south-1 (Cape Town)NoNoYes
sa-east-1 (São Paulo)NoNoYes
mx-central-1 (Mexico)NoNoYes

Geo inference details

Geo: US

Geo Inference ID: us.anthropic.claude-opus-4-5-20251101-v1:0

Source Region Destination Regions
us-east-1 (N. Virginia)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)
us-east-2 (Ohio)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)
us-west-1 (N. California)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-1 (N. California), us-west-2 (Oregon)
us-west-2 (Oregon)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)
ca-central-1 (Canada)ca-central-1 (Canada), us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)

Geo: EU

Geo Inference ID: eu.anthropic.claude-opus-4-5-20251101-v1:0

Source Region Destination Regions
eu-central-1 (Frankfurt)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-central-2 (Zurich)eu-central-1 (Frankfurt), eu-central-2 (Zurich), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-north-1 (Stockholm)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-south-1 (Milan)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-south-2 (Spain)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-west-1 (Ireland)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-west-2 (London)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-2 (London), eu-west-3 (Paris)
eu-west-3 (Paris)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)

Global inference details

Global Inference ID Americas EMEA Asia Pacific
global.anthropic.claude-opus-4-5-20251101-v1:0
  • us-east-1 (N. Virginia)

  • us-east-2 (Ohio)

  • us-west-1 (N. California)

  • us-west-2 (Oregon)

  • ca-central-1 (Canada)

  • ca-west-1 (Calgary)

  • sa-east-1 (São Paulo)

  • mx-central-1 (Mexico)

  • eu-central-1 (Frankfurt)

  • eu-central-2 (Zurich)

  • eu-north-1 (Stockholm)

  • eu-south-1 (Milan)

  • eu-south-2 (Spain)

  • eu-west-1 (Ireland)

  • eu-west-2 (London)

  • eu-west-3 (Paris)

  • il-central-1 (Tel Aviv)

  • me-central-1 (UAE)

  • me-south-1 (Bahrain)

  • af-south-1 (Cape Town)

  • ap-east-2 (Malaysia)

  • ap-northeast-1 (Tokyo)

  • ap-northeast-2 (Seoul)

  • ap-northeast-3 (Osaka)

  • ap-south-1 (Mumbai)

  • ap-south-2 (Hyderabad)

  • ap-southeast-1 (Singapore)

  • ap-southeast-2 (Sydney)

  • ap-southeast-3 (Jakarta)

  • ap-southeast-4 (Melbourne)

  • ap-southeast-5 (Auckland)

  • ap-southeast-7 (Kuala Lumpur)

Quotas and Limits

Your AWS account has default quotas to maintain the performance of the service and to ensure appropriate usage of Amazon Bedrock. The default quotas assigned to an account might be updated depending on regional factors, payment history, fraudulent usage, and/or approval of a quota increase request. For more details, please refer to Quotas documentation.

Quota Default value
Cross-region requests per minute10,000
Cross-region tokens per minute2,000,000
Max tokens per day1,440,000,000

These are default quotas shown for us-east-1. To see quotas and limits for your account, please log in to your AWS Console.

Sample Code

Step 1 - AWS Account: If you have an AWS account already, skip this step. If you are new to AWS, sign up for an AWS account.

Step 2 - API key: Go to the Amazon Bedrock console and generate a long-term API key.

Step 3 - Get the SDK: To use this getting started guide, you must have Python already installed. Then install the relevant software depending on the APIs you are using.

pip install boto3

Step 4 - Set environment variables: Configure your environment to use the API key for authentication.

AWS_BEARER_TOKEN_BEDROCK="<provide your Bedrock API key>"

Step 5 - Run your first inference request: Save the file as bedrock-first-request.py

Invoke API
import json import boto3 client = boto3.client('bedrock-runtime', region_name='us-east-1') response = client.invoke_model( modelId='anthropic.claude-opus-4-5-20251101-v1:0', body=json.dumps({ 'messages': [{ 'role': 'user', 'content': 'Can you explain the features of Amazon Bedrock?'}], 'max_tokens': 1024 }) ) print(json.loads(response['body'].read()))
Converse API
import boto3 client = boto3.client('bedrock-runtime', region_name='us-east-1') response = client.converse( modelId='anthropic.claude-opus-4-5-20251101-v1:0', messages=[ { 'role': 'user', 'content': [{'text': 'Can you explain the features of Amazon Bedrock?'}] } ] ) print(response)