AWS amazonq documentation change
Summary
Added detailed region-specific inference behavior documentation and service-specific processing locations
Security assessment
Clarifies data processing locations and encryption in transit, which informs security-conscious deployments. However, this documents existing security practices rather than addressing a specific vulnerability.
Diff
diff --git a/amazonq/latest/qdeveloper-ug/cross-region-processing.md b/amazonq/latest/qdeveloper-ug/cross-region-processing.md index 3dd0cad3c..6163f74b6 100644 --- a//amazonq/latest/qdeveloper-ug/cross-region-processing.md +++ b//amazonq/latest/qdeveloper-ug/cross-region-processing.md @@ -24 +24,3 @@ Amazon Q Developer is powered by Amazon Bedrock, and uses 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. +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. Some Amazon Q Developer features and integrations may perform inference in Regions other than where your Q Developer profile was created. For more information, see Supported regions for Amazon Q Developer cross-region inference. + +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 is encrypted while transmitted across Amazon's secure network. There's no additional cost for using cross-region inference. @@ -39,0 +42,34 @@ Asia Pacific* | Asia Pacific (Mumbai) (ap-south-1) Asia Pacific (Seoul) (ap-nor +###### Note + +The following services perform inferencing in the US East (N. Virginia) Region (us-east-1), regardless of where you create a Q Developer profile: + + * [Code suggestions in AWS Lambda](./lambda-setup.html) + + * [Code suggestions in Amazon EMR](./emr-setup.html) + + * [Code suggestions in Amazon SageMaker AI Studio](./sagemaker-setup.html) + + * [Code suggestions in AWS Glue](./glue-setup.html) + + * [Code suggestions in AWS Cloud9](./cloud9-setup.html) + + * [Amazon Q CLI in AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/q-cli-features-in-cloudshell.html) + + * [Amazon ECS task editor](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-task-definition.html) + + * [Amazon Q in Amazon SageMaker Unified Studio](https://docs.aws.amazon.com/sagemaker-unified-studio/latest/adminguide/amazonq.html) + + * [Amazon Q in Amazon OpenSearch Service](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/Amazon-Q-developer-support.html) + + + + +The following features process data in your console Region only: + + * [Amazon Q generative SQL in Amazon Redshift](https://docs.aws.amazon.com/redshift/latest/mgmt/query-editor-v2-generative-ai.html) + + + + +When you create an investigation with Amazon Q Developer operational investigations, your data may be stored and processed in other Regions. For more information, see the [Security in operational investigations](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Security.html#cross-region-inference) in the _Amazon CloudWatch User Guide_. +