AWS Security ChangesHomeSearch

AWS amazonq documentation change

Service: amazonq · 2025-04-11 · Documentation low

File: amazonq/latest/qdeveloper-ug/cross-region-processing.md

Summary

Updated cross-region processing documentation to clarify data geography boundaries, add regional routing table, and emphasize encryption during transmission

Security assessment

Added statement about data encryption during transmission qualifies as security documentation improvement, but there's no evidence of addressing a specific security vulnerability

Diff

diff --git a/amazonq/latest/qdeveloper-ug/cross-region-processing.md b/amazonq/latest/qdeveloper-ug/cross-region-processing.md
index 56269459f..3dd0cad3c 100644
--- a//amazonq/latest/qdeveloper-ug/cross-region-processing.md
+++ b//amazonq/latest/qdeveloper-ug/cross-region-processing.md
@@ -24 +24 @@ Amazon Q Developer is powered by Amazon Bedrock, and uses cross-region inference
-Today, regardless of where you use Amazon Q Developer, your data is processed in a US Region unless you're using Amazon Q generative SQL outside the US regions. With cross-region inferencing, your requests to Amazon Q Developer may be processed in any of our US regions (currently US East (N. Virginia) Region, the US West (Oregon) Region, or the US East (Ohio) Region), even if you're using Amazon Q Developer in a different AWS Region. For information on where data is stored during processing, see [Data protection](./data-protection.html). For information on where you can use Amazon Q Developer, see [Supported Regions for Amazon Q Developer](./regions.html). There's no additional cost for using cross-region inference.
+Cross-region inference requests are kept within the AWS Regions that are part of the geography where the data originally resides. For example, a request made from a Amazon Q Developer profile created in the US is kept within the AWS Regions in the US. Although cross-region inferencing doesn’t change where your data is stored, your requests and output results may move outside of the Region where the data originally resides. All data will be encrypted while transmitted across Amazon's secure network. There's no additional cost for using cross-region inference. 
@@ -26 +26,15 @@ Today, regardless of where you use Amazon Q Developer, your data is processed in
-If you use Amazon Q generative SQL outside the US regions, your data may be processed locally or across Regions to support cross-region inference, depending on your location. If you choose the Asia Pacific (Seoul) AWS Region, cross-region inference would be used for inference requests due to model availability.
+Cross region inference doesn’t affect where your data is stored. For information on where data is stored when you use Amazon Q Developer, see [Data protection in Amazon Q Developer](./data-protection.html). 
+
+### Supported regions for Amazon Q Developer cross-region inference
+
+The following table describes what Regions your requests may be routed to depending on the geography where the request originated.
+
+**Supported Amazon Q Developer geography** |  **Inference regions**  
+---|---  
+United States |  US East (N. Virginia) (us-east-1) US West (Oregon) (us-west-2) US East (Ohio) (us-east-2)  
+Europe |  Europe (Frankfurt) (eu-central-1) Europe (Ireland) (eu-west-1) Europe (Paris) (eu-west-3) Europe (Stockholm) (eu-north-1)  
+Asia Pacific* |  Asia Pacific (Mumbai) (ap-south-1) Asia Pacific (Seoul) (ap-northeast-2) Asia Pacific (Singapore) (ap-southeast-1) Asia Pacific (Sydney) (ap-southeast-2) Asia Pacific (Tokyo) (ap-northeast-1)  
+  
+*Cross-region inferencing in the Asia Pacific Regions is only supported when you use Amazon Q generative SQL in the Asia Pacific (Seoul) Region. 
+
+For a complete list of Regions where you can use Amazon Q Developer, see [Supported Regions for Amazon Q Developer](./regions.html).
@@ -30 +44 @@ If you use Amazon Q generative SQL outside the US regions, your data may be proc
-Certain requests that you make to Amazon Q Developer may require cross-region calls. Cross-region calls are API calls made by Amazon Q from one AWS Region to another AWS Region. Amazon Q makes cross-region calls when your request requires it to retrieve information from a Region different from your current Region. For example, when you ask Amazon Q questions about your AWS resources that are located in different Regions, it will make a cross-region call to access your resources and retrieve the relevant data to respond to your question. 
+Certain requests that you make to Amazon Q Developer may require cross-region calls. Cross-region calls are API calls made by Amazon Q from one AWS Region to another AWS Region. Amazon Q makes cross-region calls when your request requires it to retrieve information from a Region different from your current Region. For example, when you ask Amazon Q questions about your AWS resources that are located in different Regions, it will make a cross-region call to access your resources and retrieve the relevant data to respond to your question. In addition, if a response from Amazon Q requires information from a global AWS service endpoint, Amazon Q may make calls outside of the Region where your data is stored. For more information on global services, see [Global services](https://docs.aws.amazon.com/whitepapers/latest/aws-fault-isolation-boundaries/global-services.html) in the _AWS Fault Isolation Boundaries AWS Whitepaper_.