Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Database Performance Analyzer (DPA) > Launch SolarWinds DPA on Amazon AWS in a Linux AMI

Launch SolarWinds DPA on Amazon AWS in a Linux AMI

Created by Melanie Boyd, last modified by Melanie Boyd on Nov 20, 2017

Views: 114 Votes: 0 Revisions: 19

Amazon Marketplace lets us easily provision software in Amazon Web Services with a few clicks and a few minutes. To use SolarWinds DPA in your own Amazon AWS, complete the following steps.

  1. Log in to Amazon AWS.
  2. Select the Amazon EC2 region in which you want to launch the instance. For example: US East (N. Virginia).

    SolarWinds recommends selecting a region that contains the database instances that you will monitor with DPA.


  3. Click EC2.


  4. Click Launch Instance.

  5. On the Choose an Amazon Machine Image (AMI) panel:
    1. Click the AWS Marketplace tab.
    2. Search for SolarWinds DPA 11.1 and then click Select next to the AMI.


  6. On the Choose an Instance Type panel:

    1. Select an instance type that is at least an m3.medium, which is an economical and logical size to start monitoring your database instances with DPA. However, if you are monitoring larger numbers of database instances or very active database instances, you will need the increased resources and optimizations offered by larger instance types. You can select the size you think you'll need right now and then resize to a larger instance type later.

      For more information on changing the instance size, see this article from Amazon (© 2017 Amazon Web Services, available at, obtained on October 10, 2017).

    2. Click Next: Configure Instance Details.

  7. On the Configure Instance Details panel:

    If you've used Amazon EC2 before, you probably already have an Amazon VPC network and subnet set up. Your existing network and subnet will be selected here by default.

    1. Make sure that:

      • You've enabled Auto-assign public IP so you can connect to SolarWinds DPA from your desktop.
      • You've configured any other settings to suit your network or subnet requirements.


      • IAM role: You can create a new role if your account has the correct permissions. However, you probably need to contact your administrator and have your administrator set up an account with the correct permissions. For more information on permissions, see this Amazon document (© 2012-2017 Amazon Web Services, available at, obtained on October 10, 2017).
    2. Click Next: Add Storage.
  8. On the Add Storage panel:

    1. SolarWinds recommends:

      • 20 GB as the Size.
        Note: This size is for the DPA instance only. It does not include the DPA repository.

      • Do not select the Delete on Termination option. Having to separately delete the data volume after terminating an instance is a good precautionary practice.

    2. Click Next: Tag Instance.
  9. On the Tag Instance panel:

    1. Create the tag Name with value SolarWinds DPA to more easily recognize your instance in Amazon EC2.

    2. Click Next: Configure Security Group.

  10. On the Configure Security Group panel:

    1. Add rules that allow inbound access to at least remote desktop and the HTTP/HTTPS ports:

      Type Protocol Port Range
      RDP TCP 3389
      HTTP TCP 80
      HTTPS TCP 443
    2. If you want to restrict access to DPA to just your current IP address, change the Source for these rules to My IP. Leaving Source as Anywhere is less secure.
    3. If you want to restrict access to DPA to just people in your organization, select Custom IP and specify an IP range in CIDR notation that matches the external IP addresses used in your organization.
    4. Click Review and Launch.
  11. On the Review Instance Launch panel:

    1. Review your instance options.

    2. Click Launch.

  12. On the Select an existing key pair or create a new key pair panel:

    You now need to take care of the key pair that provides security for your AMI instance. Do one of the following:

    • Create a new key pair:
      1. Select Create a new key pair.


      2. Enter a Key pair name.
      3. Click Download Key Pair.
      4. Store this file in a secure and accessible location.
    • Choose an existing key pair:
      1. Select Choose an existing key pair.


      2. Select a secure and accessible key pair.
      3. Accept the acknowledgment.

      Do not select Proceed without a key pair.

  13. Click Launch Instances.
  14. Wait a few minutes for the provisioning and initialization to finish.


Logging in to the SolarWinds DPA Server

You can access your SolarWinds DPA server with its public hostname or IP address.

  1. On the Amazon EC2 Instances page, find:
    • The public DNS or public IP of your new SolarWinds DPA server
    • The instance ID


  2. Open a web browser to the host name or IP address of your new SolarWinds DPA server.
  3. From the web browser, log on as the DPA user. The password is the Instance ID (for example: i-12345678).
  4. First time only:
    1. Configure the DPA database repository.
    2. Agree to the EULA.
    3. Select your time zone.
    4. Start registering databases.

Registering databases for monitoring


Your SolarWinds DPA server needs to be able to connect to the databases that you want to monitor. Make sure that the security group of your databases allows SQL traffic from your EC2 instance running SolarWinds DPA.

If you encounter difficulty connecting to databases or RDS instances from your SolarWinds DPA server, see SolarWinds DPA Technical Reference: Solving Amazon EC2 and RDS Connectivity Problems.

To register databases, click Register DB Instance for Monitoring. For more information, see Register a database instance for monitoring.

How to access your EC2 instance

You can connect to the Linux AMI using SSH (make sure firewall allows SSH port). Authentication is based on a public key. For example:

ssh -i "mpit.pem"

You can create a new public key or use one already generated for multiple VMs during AMI deployment process.

Last modified