Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Database Performance Analyzer (DPA) > DPA Documentation > DPA 11.1 Installation Guide > Install DPA > Install DPA on Amazon Web Services

Install DPA on Amazon Web Services

Updated: December 20, 2017

To install DPA on a different platform, see Install DPA on Windows, Install DPA on Linux or Unix, or Install DPA on Azure Marketplace.

Before you start

Before you install Database Performance Analyzer, be sure to review the preflight checklist.


The EC2 instance containing the DPA server must meet the following requirements.

Requirement Details
IAM role permissions

An IAM role with the aws-marketplace:MeterUsage permission must be associated with the EC2 instance. This permission allows the role to contact the Metering Service API and record usage. 

A user with rights to define and assign roles can create the role in either of the following ways:

  • Create the role on the Configure Instance Details panel of the wizard (see the installation instructions below).
  • Manually create the role. See Creating an IAM Role (© 2017 Amazon Web Services, available at, obtained on December 8, 2017).

To get the aws-marketplace:MeterUsage permission, attach the AWS managed policy AWSMarketplaceMeteringFullAccess to the role. 

If a role with the required permissions is not associated with the EC2 instance, DPA reports issues with metering service availability. DPA monitoring will stop if the issue is not addressed.

For more information, see:

  • Subscribing, Launching, and Managing Products (© 2017 Amazon Web Services, available at, obtained on December 8, 2017)
  • Metering-Enabled Products (© 2017 Amazon Web Services, available at, obtained on December 8, 2017)
Access to the metadata URL

The EC2 instance must have HTTP connectivity to, which is a local IP address accessible only from within Amazon instances. The following specific endpoints must be reachable from the EC2 instance:

To validate that the EC2 instance can access the metadata service, execute the following command:


The command returns a list of available metadata items.

For more information, see Retrieving Instance Metadata.

Access to the metering service

The EC2 instance must be able to reach the AWS Metering Service (MeterUsage API). The URL is:


The region depends on where you deploy the EC2 instance with DPA. For example:

To be able to launch DPA, you must have an Internet gateway configured. The Metering Service has an endpoint on the public Internet. To access the Metering Service, your VPC (Virtual Private Cloud) must be configured to allow an outbound HTTPS connection to the public Internet.

For nmore information, see

To validate that the EC2 instance can connect to the Metering Service, execute the following command:

curl https://metering.marketplace.{region}

Replace {region} with the region where your EC2 instance is running.

You should receive a MissingAuthenticationException response from the server. This response is expected and valid.

Access to the DPA repository database server

The EC2 instance must be able to access the database server that holds the DPA repository database.

For more information, see the Amazon Virtual Private Cloud (VPCs) and Amazon RDS documentation.

Differences between AWS and self-managed servers

  • Different default ports

    You can access the SolarWinds DPA user interface on the standard HTTP port 80 and HTTPS port 443. The Windows Firewall settings have been set to allow inbound HTTP and HTTPS traffic.

  • Preconfigured administrator account: dpa

    The password is the Amazon Instance ID of the server. You can find the Instance ID in your Amazon EC2 dashboard.

Launch a DPA instance in Amazon EC2

  1. Log in to 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. Provide information on the following pages.

    Choose an AMI page
    1. Click the Community AMI tab.
    2. Enter SolarWinds DPA in the search field, and select the latest version.


    Choose an Instance Type page
    1. Select an m3.medium instance type or larger. This table lists the recommended instance types:


      General Purpose Compute optimized Memory optimized
      m3.medium c3.large r3.large
      m3.large c3.xlarge  
      m3.xlarge c3.2xlarge  

      The m3.medium type is an economical choice and a logical instance type to start with. However, large deployments and managing active databases require the increased resources and optimizations available to the larger instance types. You can select the size you need right now and then resize to a larger instance type later.

    2. Click Next: Configure Instance Details.
    Configure Instance Details Type page

    If you have used Amazon EC2 before, you may have an Amazon Virtual Private Cloud (VPC) network and subnet set up. Your existing network and subnet are selected by default.

    1. Enable Auto-assign public IP so you can connect to SolarWinds DPA from your computer.
    2. Click Next: Add Storage.
    Add Storage page
    1. You can configure additional storage beyond the default storage of 8 GB that the AMI provisions.

      The Delete on Termination option is not selected by default. SolarWinds recommends leaving this option cleared and separately deleting the data volume after terminating an instance.

    2. Click Next: Tag Instance.
    Tag Instance page
    1. Enter SolarWinds DPA in the Name tag to recognize your instance in Amazon EC2.
    2. Click Next: Configure Security Group.
    Configure Security Group page
    1. Add rules that allow inbound access to the remote desktop (RDP), HTTP, and HTTPS ports.

      Type Protocol Port Range
      HTTP TCP 80
      HTTPS TCP 443
      RDP TCP 3389
    2. To restrict access to SolarWinds DPA to only your current IP address, change the Source rules to My IP. A Source set to Anywhere is less secure.
    3. To restrict access to SolarWinds DPA to only people in your organization, select Custom IP for the Source and specify an IP range in classless inter-domain routing (CIDR) notation that matches the external IP addresses used in your organization.


    4. Click Review and Launch.
    Review Instance Launch page
    1. Review your instance options.
    2. Click Launch.
    3. If there are key pairs, the Select an existing key pair dialog opens. If not, the Create a new key pair dialog opens.
    Create a new key pair dialog

    Secure your AMI instance with a public key pair.

    • If you do not have a 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.
    • If you have a key pair:
      1. Select Choose an existing key pair.
      2. Select a secure and accessible key pair.
      3. Accept the acknowledgment.
  6. Click Launch Instances.

    The instance stage and status is displayed.


Log in to the AWS DPA server

  1. On the Amazon EC2 Instances page, locate:
    • The public domain name system (DNS) or public IP address of your new DPA server
    • The instance ID


  2. Go to the public DNS or IP address in a web browser.
  3. Log in as the dpa user. The password is the Instance ID (for example, i-12345678).
  4. Select your time zone, and finish the configuration.
Last modified