Bedrock keeps Claude traffic in Seoul, Singapore and India
AWS published two Amazon Bedrock posts on 29 September 2026 US time, 30 September in Singapore. Both move Claude inference closer to customers with local data processing rules.
- Seoul and Singapore get in-region inference. Seoul has Claude Opus 5 and Claude Sonnet 5. Singapore has Claude Sonnet 5 only.
- India gets a geographic cross-Region profile for Opus 5, Sonnet 5 and Haiku 4.5.
AWS names financial services, healthcare and the public sector as target users.
Two different residency models
The two launches work differently, and the difference matters for compliance reviews.
| Seoul and Singapore | India | |
|---|---|---|
| Mode | In-region inference | Geographic cross-Region inference |
| Regions | ap-northeast-2 or ap-southeast-1 alone | ap-south-1 and ap-south-2 |
| Model ID form | anthropic.claude-sonnet-5 | in.anthropic.claude-sonnet-5 |
| Capacity | Bounded by the one Region | Pooled across both Regions |
AWS says in-region requests have no routing layer. Prompts and outputs stay in the Region you call for the whole request.
For India, AWS says requests route only between Mumbai and Hyderabad, and prompts and outputs "might move between those two Regions."
Billing, logs and APIs stay local
For Seoul and Singapore, AWS says billing follows standard on-demand pricing for the Region you call. Quotas, CloudWatch metrics and CloudTrail entries are scoped to that same Region.
For India, AWS says billing, quotas and logs sit in the source Region, whichever backend Region served the request. It says customer data is not stored in a destination Region.
Both posts say the bedrock-runtime endpoint supports the Anthropic Messages API, InvokeModel and Converse. They also list Bedrock Guardrails and intelligent prompt routing.
The India post says Bedrock does not store inputs or outputs by default. It adds that some models require human review by AWS if automatic safety classifiers flag content.
Older models, no Opus in Singapore
Neither post lists the newer Claude Sonnet 5.5 or Claude Opus 5.5. Teams that want the latest models in these Regions should check the Bedrock regional availability table, which AWS cites as the current source.
Singapore's in-region option covers Sonnet 5 only. A Singapore workload that needs Opus 5 in-region would have to look to Seoul, which changes the residency answer.
Neither post gives per-token prices. AWS says in-region capacity is limited to one Region, so throughput can cap out under load.
The India post's Haiku 4.5 sample shows the profile ID with a stray space after "in." Copy IDs from the console.
Regulated teams in Korea, Singapore and India
Data protection and procurement teams can now ask for Claude traffic that stays in one Korean or Singaporean Region, or inside India.
- Confirm which mode you need. Single-Region and in-country are different promises.
- Update model IDs and IAM permissions. India requires permission to invoke a geographic cross-Region profile.
- Load test before moving production, since in-region throughput is bounded by one Region.
Anthropic runs its own retirement schedule for older Claude models. See Claude Sonnet 4.5 deprecated: Anthropic retires claude-sonnet-4-5-20250929 on the Claude API on 30 November. For the newest Sonnet, see Anthropic releases Claude Sonnet 5.5 on 28 September at unchanged Sonnet 5 prices.