Claude on Amazon Bedrock

Calling Claude through Bedrock slightly differs from how you would call Claude when using Anthropic's client SDK's. This guide will walk you through the process of completing an API call to Claude on Bedrock in either Python or TypeScript.

Note that this guide assumes you have already signed up for an AWS account and configured programmatic access.

Install and configure the AWS CLI

1. Install a version of the AWS CLI at or newer than version 2.13.23
2. Configure your AWS credentials using the AWS configure command (see Configure the AWS CLI) or find your credentials by navigating to "Command line or programmatic access" within your AWS dashboard and following the directions in the popup modal.
3. Verify that your credentials are working:

aws sts get-caller-identity

Install an SDK for accessing Bedrock

Anthropic's client SDKs support Bedrock. You can also use an AWS SDK like boto3 directly.

pip install -U "anthropic[bedrock]"

Accessing Bedrock

Subscribe to Anthropic models

Go to the AWS Console > Bedrock > Model Access and request access to Anthropic models. Note that Anthropic model availability varies by region. See AWS documentation for latest information.

API model IDs

For more information about regional vs global model IDs, see the Global vs regional endpoints section below.

List available models

The following examples show how to print a list of all the Claude models available through Bedrock:

aws bedrock list-foundation-models --region=us-west-2 --by-provider anthropic --query "modelSummaries[*].modelId"

Making requests

The following examples show how to generate text from Claude on Bedrock:

from anthropic import AnthropicBedrock

client = AnthropicBedrock(
    # Authenticate by either providing the keys below or use the default AWS credential providers, such as
    # using ~/.aws/credentials or the "AWS_SECRET_ACCESS_KEY" and "AWS_ACCESS_KEY_ID" environment variables.
    aws_access_key="<access key>",
    aws_secret_key="<secret key>",
    # Temporary credentials can be used with aws_session_token.
    # Read more at https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html.
    aws_session_token="<session_token>",
    # aws_region changes the aws region to which the request is made. By default, we read AWS_REGION,
    # and if that's not present, we default to us-east-1. Note that we do not read ~/.aws/config for the region.
    aws_region="us-west-2",
)

message = client.messages.create(
    model="global.anthropic.claude-sonnet-4-5-20250929-v1:0",
    max_tokens=256,
    messages=[{"role": "user", "content": "Hello, world"}]
)
print(message.content)

See our client SDKs for more details, and the official Bedrock docs here.

Activity logging

Bedrock provides an invocation logging service that allows customers to log the prompts and completions associated with your usage.

Anthropic recommends that you log your activity on at least a 30-day rolling basis in order to understand your activity and investigate any potential misuse.

Feature support

You can find all the features currently supported on Bedrock here.

PDF Support on Bedrock

PDF support is available on Amazon Bedrock through both the Converse API and InvokeModel API. For detailed information about PDF processing capabilities and limitations, see the PDF support documentation.

Important considerations for Converse API users:

• Visual PDF analysis (charts, images, layouts) requires citations to be enabled
• Without citations, only basic text extraction is available
• For full control without forced citations, use the InvokeModel API

For more details on the two document processing modes and their limitations, refer to the PDF support guide.

1M token context window

Claude Sonnet 4 and 4.5 support the 1M token context window on Amazon Bedrock.

Global vs regional endpoints

Starting with Claude Sonnet 4.5 and all future models, Amazon Bedrock offers two endpoint types:

• Global endpoints: Dynamic routing for maximum availability
• Regional endpoints: Guaranteed data routing through specific geographic regions

Regional endpoints include a 10% pricing premium over global endpoints.

When to use each option

Global endpoints (recommended):

• Provide maximum availability and uptime
• Dynamically route requests to regions with available capacity
• No pricing premium
• Best for applications where data residency is flexible

Regional endpoints (CRIS):

• Route traffic through specific geographic regions
• Required for data residency and compliance requirements
• Available for US, EU, Japan, and Australia
• 10% pricing premium reflects infrastructure costs for dedicated regional capacity

Implementation

Using global endpoints (default for Sonnet 4.5 and 4):

The model IDs for Claude Sonnet 4.5 and 4 already include the global. prefix:

from anthropic import AnthropicBedrock

client = AnthropicBedrock(aws_region="us-west-2")

message = client.messages.create(
    model="global.anthropic.claude-sonnet-4-5-20250929-v1:0",
    max_tokens=256,
    messages=[{"role": "user", "content": "Hello, world"}]
)

Using regional endpoints (CRIS):

To use regional endpoints, remove the global. prefix from the model ID:

from anthropic import AnthropicBedrock

client = AnthropicBedrock(aws_region="us-west-2")

# Using US regional endpoint (CRIS)
message = client.messages.create(
    model="anthropic.claude-sonnet-4-5-20250929-v1:0",  # No global. prefix
    max_tokens=256,
    messages=[{"role": "user", "content": "Hello, world"}]
)

Additional resources

• AWS Bedrock pricing: aws.amazon.com/bedrock/pricing
• AWS pricing documentation: Bedrock pricing guide
• AWS blog post: Introducing Claude Sonnet 4.5 in Amazon Bedrock
• Anthropic pricing details: Pricing documentation