View a markdown version of this page

Claude Opus 4.7 - Amazon Bedrock

Claude Opus 4.7

Orange rounded square icon with white radial loading or progress indicator symbol. Anthropic — Claude Opus 4.7

Model Details

Claude Opus 4.7 is an Anthropic Opus model built for coding, enterprise workflows, and long-running agentic tasks.

  • Model launch date: Apr 16, 2026

  • Model EOL date: N/A

  • End User License Agreements and Terms of Use: View

  • Model lifecycle: Active

  • Context window: 1M tokens

  • Max output tokens: 128K

  • Reasoning: Supported (thinking.type: "adaptive" only)

  • Knowledge cutoff: January 2026

  • Marketplace product ID: prod-d2ik6zgct5hxi

Important

Claude Opus 4.7 only supports thinking.type: "adaptive" for extended thinking. Unlike Claude Opus 4.6, thinking.type: "enabled" with budget_tokens is not supported and will return a 400 error. If you are migrating from Opus 4.6, update your requests to use thinking.type: "adaptive". For more information, see Adaptive thinking.

Input Modalities Output Modalities
Red circle with white X icon indicating error, cancel, or close action. AudioRed circle with white X icon indicating error, cancel, or close action. Embedding
Green circle with white checkmark icon. ImageRed circle with white X icon indicating error, cancel, or close action. Image
Red circle with white X icon indicating error, cancel, or close action. SpeechRed circle with white X icon indicating error, cancel, or close action. Speech
Green circle with white checkmark icon. TextGreen circle with white checkmark icon. Text
Red circle with white X icon indicating error, cancel, or close action. VideoRed circle with white X icon indicating error, cancel, or close action. Video

Endpoints and APIs supported

The following tables show which endpoints and APIs are supported for Claude Opus 4.7. For more information, see APIs supported by Amazon Bedrock and Endpoints supported by Amazon Bedrock.

Endpoint support

Endpoint Supported
bedrock-runtime supported
bedrock-mantle supported

APIs supported on bedrock-runtime endpoint

Messages Responses Chat Completions Converse Invoke
supported not-supported not-supported supported supported

APIs supported on bedrock-mantle endpoint

Messages Responses Chat Completions Converse Invoke
supported not-supported not-supported not-supported not-supported
Tip

Whenever possible, we recommend using the bedrock-runtime endpoint for new applications. See Endpoints supported by Amazon Bedrock for details.

Capabilities and Features

Bedrock Features

Features supported using bedrock-mantle endpoint

Features supported using bedrock-runtime endpoint

Implicit and Explicit Prompt Caching using bedrock-runtime and bedrock-mantle endpoints

For more information, see Prompt caching for faster model inference.

Explicit Prompt Caching supported Min tokens per cache checkpoint Max cache checkpoints per request Supported TTL Fields that accept prompt cache checkpoints
Yes 4,096 4 5 minutes, 1 hour system, messages, and tools

Computer use using bedrock-runtime and bedrock-mantle endpoints

For more information, see Computer use.

Tool type Beta header
computer_20251124 computer-use-2025-11-24

Pricing

This model is a third-party model offered and billed through AWS Marketplace. Charges appear on your AWS bill and in AWS Cost Explorer under the model provider (not under Amazon Bedrock). For pricing, see 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-7 N/A

us.anthropic.claude-opus-4-7

eu.anthropic.claude-opus-4-7

jp.anthropic.claude-opus-4-7

au.anthropic.claude-opus-4-7

global.anthropic.claude-opus-4-7
bedrock-mantle anthropic.claude-opus-4-7 https://bedrock-mantle.{region}.api.aws/anthropic/v1/messages N/A N/A

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/anthropic/v1/messages".

Service Tiers

Amazon Bedrock offers multiple service tiers to match your workload requirements. Standard provides pay-per-token access with no commitment (set "service_tier": "default" or omit the field). Priority delivers the fastest response times for a price premium (set "service_tier": "priority"). Flex provides lower-cost access for flexible, non-time-sensitive workloads (set "service_tier": "flex"). Reserved provides dedicated throughput with a term commitment for predictable workloads; it is set at the account level rather than per request (contact your AWS account team to enable). For more information, see service tiers.

Standard Priority Flex Reserved
Green circle with white checkmark icon. Red circle with white X icon indicating error, cancel, or close action. Red circle with white X icon indicating error, cancel, or close action. Red circle with white X icon indicating error, cancel, or close action.

Regional Availability

Regional availability at a glance

Amazon 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 (such as US, EU, and APAC) while respecting data residency, and Global Cross-Region routes anywhere worldwide when there are no residency constraints. Refer to the Regional availability by models page for more details.

Availability differs by endpoint.

Availability using the bedrock-runtime endpoint

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

Availability using the bedrock-mantle endpoint

Region In-Region Geo Global
us-east-1 (N. Virginia)supportednot-supportednot-supported
eu-north-1 (Stockholm)supportednot-supportednot-supported
eu-west-1 (Ireland)supportednot-supportednot-supported
ap-northeast-1 (Tokyo)supportednot-supportednot-supported
ap-southeast-4 (Melbourne)supportednot-supportednot-supported

Geo inference details

Geo: US

Geo Inference ID: us.anthropic.claude-opus-4-7

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)
ca-west-1 (Calgary)ca-west-1 (Calgary), us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)

Geo: EU

Geo Inference ID: eu.anthropic.claude-opus-4-7

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)

Geo: JP

Geo Inference ID: jp.anthropic.claude-opus-4-7

Source Region Destination Regions
ap-northeast-1 (Tokyo)ap-northeast-1 (Tokyo), ap-northeast-3 (Osaka)
ap-northeast-3 (Osaka)ap-northeast-1 (Tokyo), ap-northeast-3 (Osaka)

Geo: AU

Geo Inference ID: au.anthropic.claude-opus-4-7

Source Region Destination Regions
ap-southeast-2 (Sydney)ap-southeast-2 (Sydney), ap-southeast-4 (Melbourne)
ap-southeast-4 (Melbourne)ap-southeast-2 (Sydney), ap-southeast-4 (Melbourne)

Global inference details

Global Inference ID Americas EMEA Asia Pacific
global.anthropic.claude-opus-4-7
  • 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 (Taipei)

  • 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 (Malaysia)

  • ap-southeast-6 (New Zealand)

  • ap-southeast-7 (Thailand)

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 information, see Quotas for Amazon Bedrock documentation and see the limits for the model.

Default quotas for Claude Opus 4.7 are 20M input TPM and 4M output TPM on bedrock-mantle and 30M TPM on bedrock-runtime for each supported region. Claude Opus 4.7 does not have a requests-per-minute (RPM) quota; throttling is governed solely by the token-per-minute (TPM) quotas above.

Sampling parameters no longer supported

Starting with Claude Opus 4.7, temperature, top_p, and top_k parameters are no longer supported. The recommended migration path is to omit these parameters entirely from your requests and to use prompting to guide the model's behavior. If you previously relied on temperature = 0 for deterministic outputs, note that this setting did not guarantee identical responses across invocations.

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.

Messages API
pip install -U anthropic aws-bedrock-token-generator
Invoke/Converse API
pip install boto3

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

Messages API
AWS_BEARER_TOKEN_BEDROCK="<provide your Bedrock API key>"
Invoke/Converse API
AWS_BEARER_TOKEN_BEDROCK="<provide your Bedrock API key>"

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

Messages API
from anthropic import Anthropic from aws_bedrock_token_generator import provide_token token = provide_token(region="us-east-1") client = Anthropic( base_url="https://bedrock-runtime.us-east-1.amazonaws.com/anthropic", api_key=token, ) response = client.messages.create( model="global.anthropic.claude-opus-4-7", max_tokens=1024, messages=[{"role": "user", "content": "Can you explain the features of Amazon Bedrock?"}], ) print(response)
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-7', body=json.dumps({ 'anthropic_version': 'bedrock-2023-05-31', '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-7', messages=[ { 'role': 'user', 'content': [{'text': 'Can you explain the features of Amazon Bedrock?'}] } ] ) print(response)