Architecture Overview - Distributed Load Testing on AWS

Architecture Overview

Deploying this solution builds the following environment in the AWS Cloud.


        Distributed Load Testing on AWS architecture on AWS

Figure 1: Distributed Load Testing on AWS architecture

The AWS CloudFormation template deploys a distributed load tester API, which leverages Amazon API Gateway to invoke the solution's microservices (AWS Lambda functions). The microservices provide the business logic to manage test data and run the tests. These microservices interact with Amazon Simple Storage Service (Amazon S3), Amazon DynamoDB, and Amazon Simple Queue Service (Amazon SQS) to provide storage for the test scenario details and results.

The solution also deploys an Amazon Virtual Private Cloud (Amazon VPC) network topology that contains the solution’s Amazon Elastic Container Service (Amazon ECS) containers running on AWS Fargate. The containers contain a Taurus load testing Docker image which is used to generate load for testing your application’s performance. Taurus is an open-source test automation framework. AWS CodePipeline, AWS CodeBuild, and Amazon S3 help manage the image.

The solution creates a web console powered by AWS Amplify and deploys it into an Amazon S3 bucket configured for static web hosting. Amazon CloudFront is used to provide secure, public access to the solution’s website bucket contents. During initial configuration, the solution also creates a default administrator role and sends an access invite to a customer-specified user email address. The solution uses Amazon Cognito user pool to manage user access to the console and the load tester API.

After you deploy the solution, you can use the web console to create a test scenario that consists of a series of tasks. Lambda uses the test scenario to start running the Fargate tasks. When each task is complete, the results are stored in Amazon S3 and the output is logged in Amazon CloudWatch. Once all tasks are complete, the results are stored in DynamoDB.