AWS transform documentation change
Summary
Removed detailed cross-region processing documentation and moved it to a separate file. Updated links and simplified content structure.
Security assessment
The changes primarily restructure documentation about cross-region data processing without introducing new security controls or addressing vulnerabilities. While the content mentions data encryption in transit and geographic restrictions, these are existing security assurances rather than new security-related updates. No evidence of security vulnerability fixes or incident responses.
Diff
diff --git a/transform/latest/userguide/data-protection.md b/transform/latest/userguide/data-protection.md index 1fe3e55b2..ab3731ff4 100644 --- a//transform/latest/userguide/data-protection.md +++ b//transform/latest/userguide/data-protection.md @@ -5,2 +4,0 @@ -Cross-region processing - @@ -34 +32 @@ In AWS Transform, your data is stored in the AWS Region where your AWS Transform -With cross- inferencing, your requests to AWS Transform may be processed in a different Region within the geography where your data is stored. For more information, see Cross-Region inference. +With cross-inferencing, your requests to AWS Transform may be processed in a different Region within the geography where your data is stored. For more information, see [Cross-Region inference](./cross-region-processing.html#cross-region-inference). @@ -38 +36 @@ With cross- inferencing, your requests to AWS Transform may be processed in a di - * Cross-region processing in AWS Transform + * [Cross-region processing in AWS Transform](./cross-region-processing.html) @@ -47,108 +44,0 @@ With cross- inferencing, your requests to AWS Transform may be processed in a di -## Cross-region processing in AWS Transform - -The following sections describe how cross-region inference and cross-region calls are used to provide the AWS Transform service. - -### Cross-region inference - -AWS Transform is powered by Amazon Bedrock, and uses cross-region inference to distribute traffic across different AWS Regions to enhance large language model (LLM) inference performance and reliability. With cross-region inference, you get: - - * Increased throughput and resilience during high demand periods - - * Improved performance - - * Access to newly launched AWS Transform capabilities and features that rely on the most powerful LLMs hosted on Amazon Bedrock - - - - -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 AWS Transform configuration 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 doesn’t affect where your data is stored. For information on where data is stored when you use AWS Transform, see [Data protection in AWS Transform](./data-protection.html). - -#### Supported regions for AWS Transform cross-region inference - -Certain requests you make to AWS Transform might require cross-region calls. The following table describes what Regions your requests may be routed to depending on the geography where the request originated. - -Source Region | Destination Regions ----|--- -US East (N. Virginia) (us-east-1) | us-east-1us-east-2us-west-2 -Europe (Frankfurt) (eu-central-1) | eu-central-1eu-north-1eu-south-1eu-south-2eu-west-1eu-west-3 -Asia Pacific (Mumbai) (ap-south-1) | ap-northeast-1ap-northeast-2ap-northeast-3ap-south-1ap-south-2ap-southeast-1ap-southeast-2ap-southeast-4 -Asia Pacific (Tokyo) (ap-northeast-1) | ap-northeast-1ap-northeast-2ap-northeast-3ap-south-1ap-south-2ap-southeast-1ap-southeast-2ap-southeast-4 -Asia Pacific (Seoul) (ap-northeast-2) | ap-northeast-1ap-northeast-2ap-northeast-3ap-south-1ap-south-2ap-southeast-1ap-southeast-2ap-southeast-4 -Asia Pacific (Sydney) (ap-southeast-2) | ap-northeast-1ap-northeast-2ap-northeast-3ap-south-1ap-south-2ap-southeast-1ap-southeast-2ap-southeast-4 -Europe (London) (eu-west-2) | eu-central-1eu-north-1eu-south-1eu-south-2eu-west-1eu-west-2eu-west-3 -Canada (Central) (ca-central-1) | Commercial AWS Regions + ca-central-1 - -For a complete list of Regions where you can use AWS Transform, see [Supported Regions for AWS Transform](./regions.html). - -### Cross-Region knowledge - -When you ask a general question about AWS Transform services, transformation workflows, or related AWS documentation, AWS Transform might make cross-region requests to US East (Virginia) (us-east-1) for US regions or Europe (Frankfurt) (eu-central-1) for all other regions to retrieve documentation and fulfill your request. For example, when you ask questions about how to use other AWS services such as Lambda, AWS Transform might make a cross-region call to retrieve relevant AWS documentation to respond to your question. The following table describes what Regions your requests may be routed to depending on the geography where the request originated. - -Source Region | Destination Regions ----|--- -US East (N. Virginia) (us-east-1) | US East (N. Virginia) (us-east-1) -Europe (Frankfurt) (eu-central-1) | Europe (Frankfurt) (eu-central-1) -Europe (London) (eu-west-2) | Europe (Frankfurt) (eu-central-1) -Asia Pacific (Tokyo) (ap-northeast-1) | Europe (Frankfurt) (eu-central-1) -Asia Pacific (Sydney) (ap-southeast-2) | Europe (Frankfurt) (eu-central-1) -Asia Pacific (Seoul) (ap-northeast-2) | Europe (Frankfurt) (eu-central-1) -Asia Pacific (Mumbai) (ap-south-1) | Europe (Frankfurt) (eu-central-1) -Canada (Central) (ca-central-1) | Europe (Frankfurt) (eu-central-1) - -This setting is enabled by default. An account administrator can modify this setting. Disabling this feature results in the loss of access to features that require AWS Transform to retrieve knowledge from other regions. This might result in less accurate responses. - -To disable cross-region calls made by AWS Transform: - - 1. When first setting up AWS Transform, navigate to the **Get Started** page and complete the configuration. For for an existing AWS Transform configuration, navigate to the **Settings** page. - - 2. Toggle **Enable cross-region calls to answer general AWS related questions** to the _off_ position. - - - - -### AWS Transform for Windows cross-region inference - -The following table shows the source Regions from which you can call the inference profile and the destination Regions to which the requests can be routed: - -Source Region | Inference Destination Regions ----|--- -US East (N. Virginia) (us-east-1) | US East (N. Virginia) - us-east-1US East (Ohio) - us-east-2US West (Oregon) - us-west-2 -Europe (Frankfurt) (eu-central-1) | eu-central-1eu-north-1eu-south-1eu-south-2eu-west-1eu-west-3 -Asia Pacific (Tokyo) (ap-northeast-1) | All commercial regions -Asia Pacific (Sydney) (ap-southeast-2) | All commercial regions -Asia Pacific (Seoul) (ap-northeast-2) | All commercial regions -Asia Pacific (Mumbai) (ap-south-1) | All commercial regions -Canada (Central) (ca-central-1) | All commercial regions - -### AWS Transform for Migrations cross-region inference - -The following table shows the source Regions from which you can call the inference profile and the destination Regions to which the requests can be routed: - -Source Region | Inference Destination Regions ----|--- -US East (N. Virginia) (us-east-1) | All commercial regions -Europe (Frankfurt) (eu-central-1) | All commercial regions -Europe (London) (eu-west-2) | All commercial regions -Asia Pacific (Tokyo) (ap-northeast-1) | All commercial regions -Asia Pacific (Sydney) (ap-southeast-2) | All commercial regions -Asia Pacific (Seoul) (ap-northeast-2) | All commercial regions -Asia Pacific (Mumbai) (ap-south-1) | All commercial regions -Canada (Central) (ca-central-1) | All commercial regions - -### AWS Transform Custom - -AWS Transform custom is only available in US East (N. Virginia) (us-east-1) and uses Amazon Bedrock geographic cross-region inference. This means that some of your calls might be routed to AWS Regions outside of US East in the same geographic region. You can access AWS Transform custom features only from workspaces deployed in US East. - -Source Region | Inference Destination Regions ----|--- -US East (N. Virginia) (us-east-1) | US East (N. Virginia) - us-east-1US East (Ohio) - us-east-2US West (Oregon) - us-west-2 -Europe (Frankfurt) (eu-central-1) | n/a -Europe (London) (eu-west-2) | n/a -Asia Pacific (Tokyo) (ap-northeast-1) | n/a -Asia Pacific (Sydney) (ap-southeast-2) | n/a -Asia Pacific (Seoul) (ap-northeast-2) | n/a -Asia Pacific (Mumbai) (ap-south-1) | n/a -Canada (Central) (ca-central-1) | n/a - @@ -163 +53 @@ Security -Data encryption +Cross-region processing