Automated deployment - Distributed Load Testing on AWS
Launch the stack

Automated deployment

Before you launch the automated deployment, 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 15 minutes

Launch the stack

Important

This solution includes an option to send anonymized operational metrics to AWS. We use this data to better understand how customers use this solution and related services and products. AWS owns the data gathered though this survey. Data collection is subject to the AWS Privacy Policy.

To opt out of this feature, download the template, modify the AWS CloudFormation mapping section, and then use the AWS CloudFormation console to upload your template and deploy the solution. For more information, refer to the Anonymized data collection section of this guide.

This automated AWS CloudFormation template deploys Distributed Load Testing on AWS.

Note

You are responsible for the cost of the AWS services used while running this solution. For more details, visit the Cost section in this guide and refer to the pricing webpage for each AWS service used 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

    Alternatively, 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, refer to the AWS Regional Services List.

  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> 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.
    Existing VPC ID <Optional input>

    If you have a VPC that you want to use and is already created, enter the ID of an existing VPC in the same Region where the stack was deployed. For example, vpc-1a2b3c4d5e6f.
    First existing subnet <Optional input>

    The ID of the first subnet within your existing VPC. This subnet needs a route to the internet to pull the container image for running tests. For example, subnet-7h8i9j0k.
    Second existing subnet <Optional input>

    The ID of the second subnet within the existing VPC. This subnet needs a route to the internet to pull the container image for running tests. For example, subnet-1x2y3z.
    AWS Fargate VPC CIDR Block

    192.168.0.0/16

    		 If you do not provide values for an existing VPC, the CIDR block for the solution-created Amazon VPC contains the IP address for AWS Fargate.
    AWS Fargate Subnet A CIDR Block

    192.168.0.0/20

    		 If you do not provide values for an existing VPC, the CIDR block contains the IP address for the Amazon VPC subnet A.
    AWS Fargate Subnet B CIDR Block

    192.168.16.0/20

    		 If you do not provide values for an existing VPC, the CIDR block contains the IP address for the Amazon 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. 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 receive a CREATE_COMPLETE status in approximately 15 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.