AWS solutions documentation change
Summary
Updated scheduling mechanism from CloudWatch Events to EventBridge Scheduler, added security note about third-party frameworks, clarified task limits based on vCPU quotas, and removed several images.
Security assessment
The change adds a new note about security considerations for third-party testing frameworks (Taurus/JMeter/K6/Locust) including security reviews and patching requirements. This qualifies as security documentation addition. There's no evidence of a specific security vulnerability being addressed.
Diff
diff --git a/solutions/latest/distributed-load-testing-on-aws/create-test-scenario.md b/solutions/latest/distributed-load-testing-on-aws/create-test-scenario.md index 3b3776b11..6dcfda04d 100644 --- a//solutions/latest/distributed-load-testing-on-aws/create-test-scenario.md +++ b//solutions/latest/distributed-load-testing-on-aws/create-test-scenario.md @@ -34,2 +33,0 @@ Configure when the test should run: - - @@ -38,5 +36 @@ Configure when the test should run: - - - * **Run on a Schedule** \- Use cron-based scheduling to run tests automatically at regular intervals. You can select from common patterns (every hour, daily, weekly) or define a custom cron expression. - - + * **Run on a Schedule** \- Use cron-based scheduling to run tests automatically at regular intervals. You can select from common patterns (every hour, daily, weekly) or define a custom cron expression. For details on the accepted cron format, supported patterns, and constraints, refer to [Cron expression reference](./cron-expression-reference.html) in the Developer guide. @@ -53 +47 @@ When you schedule a test, the following workflow occurs: - * The API passes the parameters to a Lambda function that creates a CloudWatch Events rule scheduled to run on the specified date. + * The API passes the parameters to a Lambda function that creates an Amazon EventBridge Scheduler schedule configured to run on the specified date. @@ -55 +49 @@ When you schedule a test, the following workflow occurs: - * For one-time tests (Run Once), the CloudWatch Events rule runs on the specified date and the `api-services` Lambda function executes the test. + * For one-time tests (Run Once), the EventBridge Scheduler schedule invokes the `api-services` Lambda function at the specified date and time, which executes the test. @@ -57 +51 @@ When you schedule a test, the following workflow occurs: - * For recurring tests (Run on a Schedule), the CloudWatch Events rule activates on the specified date, and the `api-services` Lambda function creates a new rule that runs immediately and recurrently based on the specified frequency. + * For recurring tests (Run on a Schedule), the EventBridge Scheduler schedule invokes the `api-services` Lambda function immediately and on the cadence defined by the cron or rate expression until the expiry date. @@ -87,2 +80,0 @@ Choose the type of load test you want to perform: - - @@ -100 +92,7 @@ Choose the type of load test you want to perform: -**HTTP endpoint configuration** image::images/test-types.png[Select the test type to run] When "Single HTTP Endpoint" is selected, configure these settings: +###### Note + +All four test types rely on third-party components. The solution runs tests through the Taurus test automation framework, which executes JMeter, K6, or Locust depending on the test type; Single HTTP Endpoint tests are converted to a JMeter test plan and run by the bundled Apache JMeter. Before creating a test, review [Third-party testing frameworks](./security-1.html#third-party-testing-frameworks) for security considerations, license information, and patching options. + +**HTTP endpoint configuration** + +When "Single HTTP Endpoint" is selected, the solution generates a JMeter test plan from your configuration and executes it with the bundled Apache JMeter binary. Configure these settings: @@ -145,2 +142,0 @@ Configure how traffic will be distributed during your test, including multi-regi - - @@ -173 +169 @@ You can begin determining the concurrent user limits for your test by using the - 1. From the left navigation pane, under **Container Insights** , select **Performance Monitoring**. + 1. In the navigation pane, under **Container Insights** , select **Performance Monitoring**. @@ -204,3 +200 @@ The **Table of Available Tasks** displays resource availability for each selecte - * **DLT Task Limit** \- The maximum number of tasks that can be created based on your account’s Fargate limits (default: 2000). - - * **Available DLT Tasks** \- The current number of tasks available for use in the region (default: 2000). + * **DLT Task Limit** \- The maximum number of tasks that can be created based on your account’s Fargate on-demand vCPU quota. New accounts typically have a lower quota; verify your current limit in the Service Quotas console and request an increase if needed. @@ -207,0 +202 @@ The **Table of Available Tasks** displays resource availability for each selecte + * **Available DLT Tasks** \- The current number of tasks available in the region, calculated as your DLT Task Limit minus the vCPUs already in use by running Fargate tasks. @@ -211 +205,0 @@ The **Table of Available Tasks** displays resource availability for each selecte -