AWS solutions documentation change
Summary
Clarified regional deployment constraints and partition-based monitoring limitations
Security assessment
The change provides operational clarification about regional deployment boundaries but contains no security-specific content or vulnerability references. It addresses architectural limitations, not security controls.
Diff
diff --git a/solutions/latest/cost-optimizer-for-workspaces/plan-your-deployment.md b/solutions/latest/cost-optimizer-for-workspaces/plan-your-deployment.md index c9ad669aa..8b4a3224d 100644 --- a//solutions/latest/cost-optimizer-for-workspaces/plan-your-deployment.md +++ b//solutions/latest/cost-optimizer-for-workspaces/plan-your-deployment.md @@ -15 +15 @@ This section describes the [cost](./cost.html), [security](./security.html), and -You must launch the solution in an AWS Region that supports AWS Lambda, Amazon WorkSpaces, and AWS Fargate services. However, once deployed, the solution will monitor the WorkSpaces in any AWS Region. The solution can also monitor the WorkSpaces in the AWS GovCloud (US) Regions. After you deploy the solution in an AWS GovCloud (US) Region, the Amazon ECS task will pull the Docker image hosted in the AWS public Amazon ECR repository and monitor the workspaces in the AWS GovCloud (US) Region. +You must launch the solution in an AWS Region that supports AWS Lambda, Amazon WorkSpaces, and AWS Fargate services. Once deployed, the solution will monitor WorkSpaces in any supported AWS Region within the same partition. For example, a deployment in US East (N. Virginia) can monitor WorkSpaces in US West (Oregon) and other commercial regions. For AWS GovCloud, deploy the solution in AWS GovCloud (US-West) to monitor WorkSpaces in both AWS GovCloud (US-West) and AWS GovCloud (US-East). Cross-partition monitoring (for example, from a commercial region to a GovCloud region) is not supported.