AWS Measuring Agents

How to locate and use AWS based Mesuring Agents

This document describes how to launch Measuring Agents in AWS as EC2 instances. Readers are assumed to be familiar with AWS EC2 terms used in here, in particular if launching Measuring Agents manually.

Listing available AWS AMIs

We make pre-installed Measuring Agents available for everybody to use in AWS redy-to-run AMIs. No additional costs (beyong the costs charged by AWS) apply when using these images.

To obtain a list of these ready to run AMIs proceed you can use one of these options:

Via our Desktop Companion

Our Desktop Companion allows you to manage AWS Measuring Agents. You can launch and terminate agents as well as register them directly with the Real Load Portal with a few mouseclicks.

Refer to the Desktop Companion Documentation for further information.

Via the Real Load portal

Login to the Real Load portal and then head to the Measuring Agents configuration section. Then click on the AWS logo:

… and a list of available AWS AMIs will be displayed.

Via the AWS Console

Using the AWS console locate AMIs belonging to our AWS account 775953462348 in your preferred AWS region. This can be done by looking for public images owned by our account, as illustrated in this screenshot:

For example in the Sydney region (ap-southeast-2) you’ll find the above listed AMI. If you can’t find an AMI in your desired region please contact us so that we can make it available.

Launching an AMI

Via our Desktop Companion

Our Desktop Companion allows you to launch AMIs with a mouseclick.

Refer to the Desktop Companion Documentation for further information.

Via the AWS Console

Once you’ve located a suitable AMI you can launch it as you would with any other Linux image as illustrated in this section.

Configure a Security Group

In order for the AMI to be reachable from the Real Load Portal you’ll need to configure a Security Group allowing inbound connections to port 8080 as a minimum.

Set the Measuring Agent secret

In order to protect access to your Measuring Agent we strongly recommend setting a non-default secret when launching the AMI.

The secret can be set at launch time by providing User Data to the AMI as follows (replace “secret” with the secret of your choice):

#!/bin/sh
echo "AGENT_SECRET=secret" > /home/ec2-user/agent_secret.sh

(Optional) Set instance tag

If you want this instance to appear in the Desktop Companion application then you’ll have to set the “REAL_LOAD_AGENT” tag to “true” when launching.

Select the Security Group

(Optional) Select SSH key

If for some reasons you think you might need to login via SSH to the Measuring Agent instance, then select an SSH key. This is not required for normal agent operations.

Configure EC2 instance in Real Load Portal

Via our Desktop Companion

Our Desktop Companion allows you to configue EC2 instances with a mouseclick.

Refer to the Desktop Companion Documentation for further information.

Manual Configuration

Once the EC2 instance is up and running, you’ll need to configure it in the Real Load portal so that you can execute load tests from it.

Once added you can validate connectivity to the agent as shown in this screenshot:

Terminating EC2 instances

Once you’ve completed your load testing it’s important to terminate the Measuring Agent instance to avoid unwatend AWS charges.

Via our Desktop Companion

Our Desktop Companion allows you to terminate EC2 instances and remove it from the Real Load Portal configuration with a mouseclick.

Refer to the Desktop Companion Documentation for further information.

Via the AWS Console

Terminate the instace as you would terminate any other Linux instance.

Remove EC2 instance from Real Load Portal

Via our Desktop Companion

Our Desktop Companion allows you to remove Measuring Agent instances with a mouseclick.

Refer to the Desktop Companion Documentation for further information.

Manual Configuration

From the Meausring Agents menu select to delete the agent.

Alternatively you could decide to keep the agent configured and simply deactivate it. Disabling is recommended to avoid warning messages in the Portal console about failing connectivity tests.


Last modified November 9, 2021: Added desktop companion doc (e693460)