Architecture overview

Architecture diagram

Deploying this solution with the default parameters deploys the following components in your AWS account.

Distributed Load Testing on AWS architecture on AWS

Note

AWS CloudFormation resources are created from AWS Cloud Development Kit (AWS CDK) constructs.

The high-level process flow for the solution components deployed with the AWS CloudFormation template is as follows:

1. A distributed load tester API, which leverages Amazon API Gateway to invoke the solution's microservices (AWS Lambda functions).

2. The microservices provide the business logic to manage test data and run the tests.

3. These microservices interact with Amazon Simple Storage Service (Amazon S3), Amazon DynamoDB, and AWS Step Functions to provide storage for the test scenario details and results and run test scenarios.

4. An Amazon Virtual Private Cloud (Amazon VPC) network topology is deployed containing the solution’s Amazon Elastic Container Service (Amazon ECS) containers running on AWS Fargate.

5. The containers include the Taurus load testing Open Container Initiative (OCI) compliant container image, which is used to generate load for testing your application’s performance. Taurus is an open-source test automation framework. The container image is hosted by AWS in an Amazon Elastic Container Registry (Amazon ECR) public repository. For more information about the ECR image repository, refer to Container image customization.

6. A web console powered by AWS Amplify is deployed it into an Amazon S3 bucket configured for static web hosting.

7. Amazon CloudFront provides secure, public access to the solution’s website bucket contents.

8. During initial configuration, this solution also creates a default solution administrator role (IAM role) and sends an access invite to a customer-specified user email address.

9. An Amazon Cognito user pool manages user access to the console and the distributed load tester API.

10. After you deploy this solution, you can use the web console to create a test scenario that defines a series of tasks.

11. The microservices use this test scenario to run Amazon ECS on AWS Fargate tasks in the Regions specified.

12. In addition to storing the results in Amazon S3 and DynamoDB, once the test is complete the output is logged in Amazon CloudWatch.

13. If you select the live data option, the solution sends the Amazon CloudWatch logs for the AWS Fargate tasks to a Lambda function during the test, for each Region in which the test was run.

14. The Lambda function then publishes the data to the corresponding topic in AWS IoT Core in the Region where the main stack was deployed. The web console subscribes to the topic, and you can see the data while the test runs in the web console.