AWS solutions documentation change
Summary
Updated region availability tables and added deployment notes for Distributed Load Testing solution. Replaced Amazon Cognito reference with general AWS services note, restructured region tables to include region codes, added US West (N. California) deployment limitation, expanded MCP Server regions, and added multi-region deployment tip.
Security assessment
The changes are administrative updates to region availability tables and deployment instructions. No security vulnerabilities, weaknesses, or incident responses are mentioned. The updates focus on service availability and deployment methods without introducing security features or addressing security flaws.
Diff
diff --git a/solutions/latest/distributed-load-testing-on-aws/plan-your-deployment.md b/solutions/latest/distributed-load-testing-on-aws/plan-your-deployment.md index 5287230f9..28140e7aa 100644 --- a//solutions/latest/distributed-load-testing-on-aws/plan-your-deployment.md +++ b//solutions/latest/distributed-load-testing-on-aws/plan-your-deployment.md @@ -15,2 +14,0 @@ This section describes cost, security, supported Regions, quotas, and other cons -This solution uses the Amazon Cognito service, which is not currently available in all AWS Regions. For the most current availability of AWS services by Region, see the [AWS Regional Services List](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/). - @@ -19 +17,5 @@ Distributed Load Testing on AWS is available in the following AWS Regions: -Region name | +###### Note + +For the most current availability of the AWS services used in this solution by Region, refer to the [AWS Regional Services List](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/). + +Region name | Region code @@ -21,8 +23,18 @@ Region name | -US East (Ohio) | Asia Pacific (Tokyo) -US East (N. Virginia) | Canada (Central) -US West (Northern California) | Europe (Frankfurt) -US West (Oregon) | Europe (Ireland) -Asia Pacific (Mumbai) | Europe (London) -Asia Pacific (Seoul) | Europe (Paris) -Asia Pacific (Singapore) | Europe (Stockholm) -Asia Pacific (Sydney) | South America (São Paulo) +US East (N. Virginia) | us-east-1 +US East (Ohio) | us-east-2 +US West (N. California)* | us-west-1 +US West (Oregon) | us-west-2 +Canada (Central) | ca-central-1 +Europe (Frankfurt) | eu-central-1 +Europe (Ireland) | eu-west-1 +Europe (London) | eu-west-2 +Europe (Paris) | eu-west-3 +Europe (Stockholm) | eu-north-1 +Asia Pacific (Mumbai) | ap-south-1 +Asia Pacific (Tokyo) | ap-northeast-1 +Asia Pacific (Seoul) | ap-northeast-2 +Asia Pacific (Singapore) | ap-southeast-1 +Asia Pacific (Sydney) | ap-southeast-2 +South America (São Paulo) | sa-east-1 + +* US West (N. California) supports deployment through [Launch Wizard](./deploy-using-aws-launch-wizard.html) only. CloudFormation console deployment does not work in this Region. @@ -32 +44 @@ Asia Pacific (Sydney) | South America (São Paulo) -If you plan to deploy the optional MCP Server integration, you must deploy the solution in an AWS Region where AWS AgentCore Gateway is available. The MCP Server feature is only available in the following AWS Regions: +If you plan to deploy the optional MCP Server integration, you must deploy the solution in an AWS Region where AgentCore Gateway is available. The MCP Server feature is only available in the following AWS Regions: @@ -36,0 +49 @@ US East (N. Virginia) | us-east-1 +US East (Ohio) | us-east-2 @@ -38,3 +51 @@ US West (Oregon) | us-west-2 -Asia Pacific (Singapore) | ap-southeast-1 -Asia Pacific (Sydney) | ap-southeast-2 -Asia Pacific (Tokyo) | ap-northeast-1 +Canada (Central) | ca-central-1 @@ -44,0 +56,11 @@ Europe (Paris) | eu-west-3 +Europe (Stockholm) | eu-north-1 +Asia Pacific (Mumbai) | ap-south-1 +Asia Pacific (Tokyo) | ap-northeast-1 +Asia Pacific (Seoul) | ap-northeast-2 +Asia Pacific (Singapore) | ap-southeast-1 +Asia Pacific (Sydney) | ap-southeast-2 +South America (São Paulo) | sa-east-1 + +For the most current availability of AgentCore Gateway by Region, refer to [Amazon Bedrock AgentCore endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/bedrock_agentcore.html) in the _AWS General Reference_. + +###### Tip @@ -46 +68 @@ Europe (Paris) | eu-west-3 -For the most current availability of AWS AgentCore Gateway by Region, refer to [AWS AgentCore Gateway endpoints and quotas](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-regions.html) in the _AWS AgentCore Gateway Developer Guide_. +If you want to use the MCP Server but need to send load testing traffic from an AWS Region where AgentCore Gateway is not supported, you can deploy the main hub stack (with the MCP Server enabled) in a supported AgentCore Gateway Region and then deploy the regional stack (see [Multi-Region deployment](./multi-region-deployment.html)) in the AWS Region where you want to generate test traffic. This allows you to use the MCP Server for AI-assisted analysis while still running load tests from your desired Region.