In this section:

Using a Manual Cloud Machine Configuration

This section describes how to launch a Load Test remote machine in the Amazon cloud and use it in a load test.

Requirements

• The AWS machine must satisfy Load Test minimal hardware requirements. See System Requirements.
• You must have an existing security group or create a new security group (described in the following section) with port 8189 open. 

Launching a Load Test Agent in AWS

1. Log into the AWS console and choose IMAGES > AMIs.
2. Choose Public Images from search menu and search for the "Parasoft Load Test" agent. This agent is a public AMI available in all regions.
3. Choose the Parasoft Load Test Agent AMI version that matches your version of Load Test and click Launch.
   

4. Choose an instance type that matches the expected load. 

   Some instances, such as T2 instances, can be only launched into a Virtual Private Cloud (VPC), while other instances, such as M3 instances, can be launched into the EC2-Classic network. If you choose a VPC type instance, you need to make sure that your instance will receive an IPv4 address. For example, a VPC type instance launched in a default subnet receives a public IPv4 address, while other VPC configurations may not receive a IPv4 address automatically. Each EC2-Classic type instance automatically receives an IPv4 address. For more information see Amazon EC2 and Amazon Virtual Private Cloud [https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html#differences-ec2-classic-vpc] section of the AWS documentation.

5. Configure the instance. No changes are required for EC2-Classic type instances. For VPC type make sure your instance will receive a public IPv4 address.

6. Set the storage to 20 GiB.
7. (Optional) Add tags. We recommend at least adding a name tag, for example, Key=Name, Value=Parasoft Load Test Agent 9.10.3.

8. Create a new security group if you are launching a Load Test Agent AMI for the first time. You can call it "Parasoft Load Test Agent" for clarity. A security group must have the following rule to allow Load Test Controller to Agent communication:
   

   Type	Custom TCP Rule
   Protocol	TCP
   Port Range	8189
   Source	0.0.0.0/0 to allow communication from all IPs. You can also limit to the IP rule of your choice.
   Description	Load Test Agent Port

   Add an SSH port to the group if you are planning to SSH to the instance you are launching.

9. Choose Proceed without a key pair. If you are planning to SSH to the instance, choose an existing key pair or create a new one.

Configuring Load Test Machines

Complete the following steps after launching an AWS instance:

1. Create a new Load Test remote machine in the Load Test Configuration tree and copy its DNS name or IPv4 address into the Host field of the machine configuration panel.
2. Right-click on the machine node and choose Verify to check if the machine is ready. It may take a minute or two for the Load Test Agent to start after an AWS instance has been launched.

At this point you can treat the machine in the Cloud as a regular remote machine. For more information on operations on remote machines see Running Load Tests on Remote Machines.

Running Distributed Load Tests in the Cloud on Machines with Different Locales

Note: This applies only to machines that are using the Japanese or Chinese language in their locale and is related to the Load Test’s support of these languages in appropriate locales.

If your Load Test controller (master) is running on a machine with a Japanese or Chinese locale and you have remote Cloud machines in your Load Test configuration, the remote machines must have the same locale as the master machine.

If you are using remote Load Test machines in a Cloud provider like Amazon Cloud these machines might not have localization settings that match the global region where they have been launched. For example, an AWS machine created from an Amazon Linux image in the Tokyo region may have the user language set to English and not Japanese. If your Load Test controller/master is using a Japanese locale, this will cause remote machines to function improperly. See Running a Distributed Load Test on Machines with Different Locales for more information.