AWS Distributed Load Balance Cloudformation Step-By-Step Tutorial

Step 1:

An Amazon API Gateway API invokes the solution’s microservices (AWS Lambda functions).

Step 2:

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

Step 3:

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

Step 4:

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

Step 5:

The containers include a 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.

Step 6

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

Step 7

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

Step 8

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

Step 9

An Amazon Cognito user pool manages user access to the console and the API Gateway API.

Step 10

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

Step 11

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

Step 12

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

Step 13

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

Step 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.

Cloudformation Template: https://solutions-reference.s3.amazonaws.com/distributed-load-testing-on-aws/latest/distributed-load-testing-on-aws.template

Documentation:

https://docs.aws.amazon.com/pdfs/solutions/latest/distributed-load-testing-on-aws/distributed-load-testing-on-aws.pdf

Jmeter for Bigners:https://www.youtube.com/playlist?list=PLUDwpEzHYYLs33uFHeIJo-6eU92IoiMZ7