Amazon Bedrock expands Claude model availability to in-country inferencing in India

Amazon Bedrock now serves Anthropic's Claude Opus 5, Claude Sonnet 5, and Claude Haiku 4.5 to customers in India through a new India geographic cross-Region inference profile that routes requests only between the ap-south-1 (Mumbai) and ap-south-2 (Hyderabad) AWS Regions. The India regional endpoint, available on the bedrock-runtime endpoint and supporting Anthropic's Messages API plus Bedrock's InvokeModel and Converse APIs, lets customers process data within India while drawing on a broader compute pool; customer data is not stored in a destination Region and remains in the source Region under Bedrock's zero data retention model, with billing, quotas, CloudWatch, and CloudTrail logs tracked in the source Region.

Artificial Intelligence https://aws.amazon.com/blogs/machine-learning/ Amazon Bedrock expands Claude model availability to in-country inferencing in India We’re excited to announce the availability of Anthropic’s Claude Opus 5 https://aws.amazon.com/blogs/machine-learning/introducing-claude-opus-5-on-aws-anthropics-most-capable-opus-model/ , Claude Sonnet 5 https://aws.amazon.com/blogs/machine-learning/introducing-claude-sonnet-5-on-aws-anthropics-most-capable-sonnet-model/ , and Claude Haiku 4.5 https://aws.amazon.com/about-aws/whats-new/2025/10/claude-4-5-haiku-anthropic-amazon-bedrock/ in India. The India regional endpoint is served through geographic cross-Region inference https://docs.aws.amazon.com/bedrock/latest/userguide/geographic-cross-region-inference.html . Customers in India can now access these models on Amazon Bedrock while processing the data in the India Regions in addition to the already supported global cross-Region inference https://docs.aws.amazon.com/bedrock/latest/userguide/global-cross-region-inference.html . This can be useful when customers need to meet the requirements to process data locally in a desired geography. In this post, we discuss how India geographic cross-Region inference works from the Mumbai and Hyderabad Regions on Amazon Bedrock for Anthropic Claude models. We also show how to get started from the Amazon Bedrock console and with code, using Anthropic’s Messages API, Amazon Bedrock InvokeModel API, and Converse API. India inference To help you achieve the scale of your AI applications, Amazon Bedrock offers cross-Region inference profiles, a feature you can use to distribute inference across multiple AWS Regions without having to manage capacity in each Region. The request originates from your source Region where you make the API call and is automatically routed to one of the destination Regions defined in the inference profile. The India geographic profile keeps inference within India. Requests route only between ap-south-1 and ap-south-2. Your input prompts and output results might move between those two Regions. Instead of being bound to the capacity of one Region, your requests draw on a broader pool of compute. This helps you maintain throughput and consistent performance under load, which matters most during traffic peaks. Cross-Region inference operates through the secure AWS network with end-to-end encryption for data in transit. Customer data is not stored in a destination Region when using cross-Region inference. It remains exclusively within the source Region. Amazon Bedrock uses a zero data retention ZDR data security model. This means that by default, Amazon Bedrock does not store model inputs or outputs. However, certain models require human review by AWS as a condition if content is flagged by automatic safety classifiers. For more details, see Data retention https://docs.aws.amazon.com/bedrock/latest/userguide/data-retention.html in the Amazon Bedrock User Guide. Billing and quota consumption are tracked against your account in the source Region, regardless of which backend Region handled the request. Amazon CloudWatch and AWS CloudTrail record log entries in the source Region only, so your monitoring stays in one place. Geographic cross-Region inference is available on the bedrock-runtime endpoint. It supports Anthropic’s Messages https://docs.aws.amazon.com/bedrock/latest/userguide/inference-messages-api.html API and the native Amazon Bedrock InvokeModel https://docs.aws.amazon.com/bedrock/latest/userguide/inference-api.html and Converse https://docs.aws.amazon.com/bedrock/latest/userguide/conversation-inference.html APIs, along with Amazon Bedrock features such as Amazon Bedrock Guardrails https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails.html and intelligent prompt routing https://docs.aws.amazon.com/bedrock/latest/userguide/prompt-routing.html . Access Claude models from the Amazon Bedrock console You can access Claude models in the text playground in the Amazon Bedrock console, which requires no coding or SDK setup. You can send prompts, adjust inference parameters, and switch between variants to get a feel for each model before you integrate the API. 1. Open the Amazon Bedrock console https://console.aws.amazon.com/bedrock/ in the Region that you want to use as the source. 2. In the navigation pane, under Test , choose Playground . 3. Choose Select model in the middle of the page. 4. Search for Anthropic Claude Opus 5, select IN Anthropic Claude Opus 5 as the inference profile under Inference , and choose Apply . 5. Enter a prompt and choose Run to generate a response. Call Claude models with the Anthropic Messages API and Amazon Bedrock InvokeModel and Converse API You can access Anthropic’s Claude Opus 5, Claude Sonnet 5, or Claude Haiku 4.5 programmatically with the India geographic inference profile ID using the Anthropic Messages API https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-anthropic-claude-messages.html on bedrock-runtime through the Anthropic SDK, or keep using the InvokeModel https://docs.aws.amazon.com/bedrock/latest/userguide/inference-api.html and Converse https://docs.aws.amazon.com/bedrock/latest/userguide/conversation-inference.html APIs on bedrock-runtime through the AWS Command Line Interface AWS CLI https://aws.amazon.com/cli/ and AWS SDK https://aws.amazon.com/developer/tools/ . Prerequisites 1. Active AWS account with Amazon Bedrock access. 2. AWS CLI installed and configured. 3. Python 3.8+. 4. Boto3 installed: pip install boto3 . 5. Anthropic SDK installed: pip install anthropic . 6. The Bedrock Token Generator for Amazon Bedrock model inference authentication installed: pip install aws bedrock token generator . 7. AWS Identity and Access Management https://aws.amazon.com/iam/ IAM role or user has the necessary permissions https://docs.aws.amazon.com/bedrock/latest/userguide/geographic-cross-region-inference.html geographic-cris-iam-setup to invoke Amazon Bedrock models using a geographic cross-Region inference profile. Here’s a quick example using the AWS SDK for Python Boto3 with the InvokeModel API: You can also use the Amazon Bedrock Converse API for a unified multi-model experience: You can also use the Anthropic Messages API using the anthropic SDK package for a streamlined experience: You can monitor usage, performance, and costs through CloudWatch https://docs.aws.amazon.com/bedrock/latest/userguide/monitoring.html and AWS Cost Explorer https://aws.amazon.com/aws-cost-management/aws-cost-explorer/ to scale your applications as demand grows. Conclusion With the launch of Anthropic’s Claude Opus 5, Claude Sonnet 5, and Claude Haiku 4.5 using Amazon Bedrock with India geographic cross-Region inference, you can now build highly scalable, resilient generative AI applications while keeping inference within the country. To get started, access Anthropic’s Claude models in the Amazon Bedrock console https://console.aws.amazon.com/bedrock/ , or call them with the API using the India geographic inference profile ID. For the most current information about model availability in each Region, see Regional availability by models https://docs.aws.amazon.com/bedrock/latest/userguide/models-region-compatibility.html model-regions-anthropic in the Amazon Bedrock User Guide.