Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > Use Amazon Cloud Services as a WPM playback location

Use Amazon Cloud Services as a WPM playback location

Created by Karen Valdellon_ret, last modified by carolyn.mazenko on May 02, 2018

Views: 927 Votes: 0 Revisions: 5

Updated May 2, 2018


This article describes how to sign up for Amazon Web Services (AWS) and use it as a playback location by installing a WPM player.


All WPM versions


Note: For a listing of what regions are currently available see, AWS Global Infrastrucutre.  (© 2016 Amazon Web Services, Inc., available at, obtained on September 1, 2016.) For information about using Amazon Elastic Compute Cloud in the AWS GovCloud (US) Region, see AWS GovCloud (US) Region.  (© 2016 Amazon Web Services, Inc., available at, obtained on September 1, 2016.) 

Sign up for Amazon Web Services

  1. Sign up for Amazon Web Services at  (© 2016 Amazon Web Services, Inc., available at, obtained on September 1, 2016.) 
  2. Fill out all the information requested for your account.
  3. Log in to the AWS Management Console at  (© 2016 Amazon Web Services, Inc., available at, obtained on September 1, 2016.) 
  4. On the EC2 tab, click Sign Up for Amazon EC2.
  5. Enter your credit card information and click Continue.
  6. Provide a phone number for Amazon's verification requirements.
  7. On the final page of the signup process, click Complete Sign Up.

Start a Windows 2008 instance

  1. Log in to the AWS Management Console at  (© 2016 Amazon Web Services, Inc., available at, obtained on September 1, 2016.) 
  2. Select the region you want to create this virtual machine in.
  3. Click Launch Instance.
  4. On the Quick Start tab, locate and select Microsoft Windows Server 2008 Base.
  5. Accept the default settings on the first Instance Details page of the wizard and click Continue.
  6. Accept the default settings on the second Instance Details page of the wizard and click Continue.
  7. Provide a name for this instance in the Value column and click Continue.
  8. Create a public/private key pair for securing your instances. 
    • Select a Key Pair If you have already created one.
    • If you have not created a Key Pair, enter a name, for example MyKeyPair, and click Create & Download your Key Pair. 
      Save the file (MyKeyPair.pem) locally. You will need this for a future step.
  9. On the Configure Firewall page, select an existing Security Group or create a new one.  Security Groups define what inbound network connections will be allowed to your new instance.  You will still need to configure the Windows Firewall on your instance to accept this traffic. For the SUM Player, create a group (“SumPlayerSecurity”) and add two rules:
    • Port: 3389 (RDP), Source:
    • Port: 17781 (HTTP*),  Source: 
  10. On the Review page of the Request Instance Wizard, verify your settings and  click Launch to start your instance.

Connect to your new instance remotely

  1. On the AWS Management Console, select Instances from the Navigation window on the left.
  2. Locate and select the instance you want to connect to in the list of instances. 
  3. From the Instance Action list, select Get Windows Admin Password. 
    Note: It takes a few minutes after the instances starts up before this will work.  If the instance is not yet ready, the Not available yet error will appear.
  4. Enter the private key from the Key Pair you used to create this instance. This is the contents of the MyKeyPair.pem file you downloaded previously. Paste the entire file’s contents and then click Decrypt Password.
  5. Start Remote Desktop and connect to this instance.  Log in as Administrator and use the decrypted password that was displayed.
  6. After you are connected to Remote Desktop, you can change the Administrator password. At this point, the instance is just another virtual machine.

Stop and terminate your instance

Note: Amazon will bill you for the time your instance is running.  If this instance is no longer required, perform the following:

  1. Select the instance and click the Instance Actions menu.
  2. Select Terminate and the instance and all its data will be deleted.
    Note: If you want to stop the instance but would like to be able to start it again, select Stop. This will stop the instance, but will keep the instance and disk image available to restart at another time.  You will be charged for the storage used for the disk image (volume), but not for the actual stopped instance.

Install the WPM Player

  1. Connect to the instance via Remote Desktop.
  2. Add an inbound rule to the Windows Firewall for the SEUM Communications Port 17781. Enter the following command at the command prompt:
    netsh advfirewall firewall add rule name = SUMPlayer dir = in protocol = tcp action = allow localport = 17781
  3. Turn off IE Enhanced Security
    1. Go to Start > Administrative Tools > Server Manager.
    2. Click Configure IE ESC.
    3. Select Off for both Administrators and for Users.
    4. Click OK.
  4. The EC2 image has C:\ProgramData\Application Data as a Junction to S:\ProgramData but there is no S drive. Remove the junction and create the directory so that the log files will work correctly executing the following from a command prompt:
    • rmdir “C:\ProgramData\Application Data”
    • mklink /J “C:\ProgramData\Application Data” C:\ProgramData
  5. Install the agent. 
  6. Go to Start > All Programs > Solarwinds Orion > Web Performance Monitor > WPM > Playback Agent Settings. 
  7. Change the password for the Player and then click Save.
  8. Add this new location to your WPM installation.

Note: An EC2 instance has its own public IP address. This address is constant while the instance is running. If you stop and then restart the instance, it will have a different public IP address (and hostname). In order to keep a stable IP Address even when the instance is off, you can assign the instance an Elastic IP. An Elastic IP is an address that is assigned/reserved for your AWS account. While the address is attached to a running instance, you are not charged for the IP (just for the instance).  If the Elastic IP is not assigned to any running instances, you are charged a small fee.  


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified