AWS has extended Amazon Bedrock's geographic cross-Region inference to India, making Anthropic's Claude Opus 5, Claude Sonnet 5 and Claude Haiku 4.5 available with in-country processing.
The India profile routes requests only between the Mumbai (ap-south-1) and Hyderabad (ap-south-2) regions. Inputs and outputs may move between those two regions but, according to AWS, do not leave India. This sits alongside the existing global cross-Region inference option, giving customers a choice when local processing is a requirement rather than a preference.
Access works the same way as other Bedrock inference profiles: through the console playground by selecting the "IN" variant of a model, or programmatically via Anthropic's Messages API, or Bedrock's native InvokeModel and Converse APIs. Bedrock features like Guardrails and intelligent prompt routing carry over.
On data handling, AWS says cross-Region inference runs over its encrypted internal network and that customer data is not stored in a destination region — it stays in the source region. Bedrock's default zero data retention model means inputs and outputs are not stored, though AWS notes certain models require human review if content is flagged by automatic safety classifiers. Billing, quota consumption, and CloudWatch/CloudTrail logging remain tied to the account's source region regardless of which backend region actually served the request.
AWS frames the change around scale and resilience: distributing inference across two regions instead of depending on capacity in one helps maintain throughput during traffic peaks, while still satisfying a need to keep data processing inside a specific geography.