Automated Deployment - Distributed Load Testing on AWS
Launch the Stack

Automated Deployment

Before you launch the automated deployment, please review the architecture and other considerations discussed in this guide. Follow the step-by-step instructions in this section to configure and deploy Distributed Load Testing on AWS into your account.

Time to deploy: Approximately 20 minutes

Launch the Stack

This automated AWS CloudFormation template deploys Distributed Load Testing on AWS in the AWS Cloud.

Note

You are responsible for the cost of the AWS services used while running this solution. See the Cost section for more details. For full details, see the pricing webpage for each AWS service you will be using in this solution.

  1. Sign in to the AWS Management Console and click the button below to launch the distributed-load-testing-on-aws AWS CloudFormation template.

    Distributed Load Testing on AWS launch button

    You can also download the template as a starting point for your own implementation.

  2. The template is launched in the US East (N. Virginia) Region by default. To launch this solution in a different AWS Region, use the region selector in the console navigation bar.

    Note

    This solution uses Amazon Cognito, which is currently available in specific AWS Regions only. Therefore, you must launch this solution in an AWS Region where Amazon Cognito is available. For the most current service availability by region, see the AWS service offerings by region.

  3. On the Create stack page, verify that the correct template URL shows in the Amazon S3 URL text box and choose Next.

  4. On the Specify stack details page, assign a name to your solution stack.

  5. Under Parameters, review the parameters for the template and modify them as necessary. This solution uses the following default values.

    Parameter Default Description
    Admin Name <Requires input> The user name for the initial solution administrator
    Admin Email <Requires input> Email address of the administrator user. After launch, an email will be sent to this address with console login instructions.
    AWS Fargate VPC CIDR Block 192.168.0.0/16 CIDR block for the solution-created Amazon VPC that will contain AWS Fargate
    AWS Fargate Subnet A CIDR Block 192.168.0.0/20 CIDR block for VPC subnet A
    AWS Fargate Subnet B CIDR Block 192.168.16.0/20 CIDR block for VPC subnet B
    AWS Fargate Security Group CIDR Block 0.0.0.0/0 CIDR block that restricts Amazon ECS container outbound access

  6. Choose Next.

  7. On the Configure stack options page, Choose Next.

  8. On the Review page, review and confirm the settings. Be sure to check the box acknowledging that the template will create AWS Identity and Access Management (IAM) resources.

  9. Choose Create stack to deploy the stack.

    You can view the status of the stack in the AWS CloudFormation console in the Status column. You should see a status of CREATE_COMPLETE in approximately 20 minutes.

Note

In addition to the primary AWS Lambda function, this solution includes the custom-resource Lambda function, which runs only during initial configuration or when resources are updated or deleted.

When running this solution, the custom-resource Lambda function is inactive. However, do not delete this function as it is necessary to manage associated resources.