Bedrock adds in-region inference for Claude Opus 5, Sonnet 5

The update puts a specific kind of guarantee in front of customers: a request sent to the Seoul (ap-northeast-2) or Singapore (ap-southeast-1) Region is served by that Region alone, with no routing layer like the one used by cross-Region inference profiles. Input prompts and output results stay inside it for the full lifecycle of the request. That matters most to organizations whose data residency rules are strict enough that multi-Region routing is not an option, and the post names financial services, healthcare, and the public sector as examples.

The trade-off is stated just as plainly. Because the request cannot be routed elsewhere, throughput is bounded by that Region's capacity, and requests are subject to per-Region service quotas. Billing follows standard on-demand pricing for the Region you call, and the operational footprint is deliberately narrow: quota consumption, CloudWatch metrics, and CloudTrail log entries are all scoped to that same Region, so there is no source-versus-destination distinction to track in monitoring. For teams already using Amazon Bedrock Guardrails and intelligent prompt routing, the post says those features remain available alongside in-region inference.

Whether this is the right fit comes down to how a team weighs residency against headroom. The guarantee that data never leaves the Region is what some regulated workloads need to proceed, but it also means the ceiling moves with that Region's capacity rather than being smoothed across a wider footprint. Teams with spiky or very large demand may find the per-Region quotas to be the deciding constraint, while those whose main obstacle was data residency get a path to run these models at scale.