AI Infrastructure
AWS Transform Keeps Storage Local but Changes Mumbai and Seoul Chat Processing
AWS Transform Chat requests from Mumbai and Seoul can be processed across commercial AWS Regions from October 7. AWS says data storage stays in the originating Region, while prompts and outputs may be processed elsewhere. The current documentation makes storage residency and inference geography different questions.
Citation-ready: AWS's effective October 7 notice permits Transform Chat inference from Mumbai and Seoul across commercial Regions while keeping stored data in the originating Region.
Evidence boundary: Current AWS documentation and document history. No customer configuration, packet trace or contractual assessment was performed. This is an effective-date follow-up, not an October 8 launch or legal compliance opinion.
What happened and why it matters
Residency reviews need separate fields for stored data, inference requests and documentation retrieval. A true statement about one field can still leave another data path unresolved.
Primary evidence
Primary reference: AWS Transform cross-region processing documentation and history. Kaleido Field checked the event date and the article's attributed facts against this source.
| Source date | October 7, 2026 effective date; September 25 notice; checked October 8 |
|---|---|
| Checked by Kaleido Field | October 8, 2026, CST |
| Source function | AI infrastructure -> processing geography and configuration evidence |
Read the exception before relying on the general rule
The page first describes geography-based inference, then adds an Important notice for Transform Chat requests originating in ap-south-1 and ap-northeast-2. From October 7 those requests can route across commercial AWS Regions. AWS says only prompts and outputs may be processed elsewhere and transmission remains encrypted.
A residency inventory should record that exception explicitly instead of copying the introductory rule. Preserve the source notice date, effective date and date you checked it. This article retains the September 25 announcement context while following the October 7 operational change.
The knowledge toggle answers a different question
The same page describes cross-region calls for general AWS documentation knowledge and a default-enabled setting administrators can disable. It separately lists inference paths for Windows, migrations, mainframe and custom transformations. Do not assume that a knowledge-retrieval toggle switches off every inference route.
Review the exact service mode, source Region and effective settings before submitting sensitive material. Ask the account owner to validate the governing agreement and data classification. The local sandbox article makes a parallel distinction: where a tool runs is not automatically where the model processes its inputs.
Evidence boundary
Current AWS documentation and document history. No customer configuration, packet trace or contractual assessment was performed. This is an effective-date follow-up, not an October 8 launch or legal compliance opinion.
FAQ
Does unchanged storage location prove prompts remain in the original Region?
No. AWS explicitly says input prompts and output results may be processed in another Region under the October 7 change.