Running PMM Server Using AWS Marketplace

You can run an instance of PMM Server hosted at AWS Marketplace. This method replaces the outdated method where you would have to accessing an AMI (Amazon Machine Image) by using its ID, different for each region.


The home page of PMM in AWS Marketplace.

Assuming that you have an AWS (Amazon Web Services) account, locate Percona Monitoring and Management Server in AWS Marketplace.

The Pricing Information section allows to select your region and choose an instance type in the table that shows the pricing for the software and infrastructure hosted in the region you have selected (the recommended EC2 instance type is preselected for you). Note that actual choice will be done later, and this table serves the information purposes, to plan costs.


As soon as you select your region, you can choose the EC2 instance in it and see its price. PMM comes for no cost, you may only need to pay for the infrastructure provided by Amazon.

Clicking the Continue to Subscribe button will proceed to the terms and conditions page. Clicking Continue to Configuration there will bring a new page to start setting up your instance.


Percona Monitoring and Management on AWS Marketplace - launch options.

Available launch options in the drop-down menu include Launch from Website and Launch through EC2. The first one is a quick way to make your instance ready. For more control, use the Manual Launch through EC2 option.

In this chapter

Setting Up a PMM Instance Using the website GUI

Choose Launch from Website option, your region, and the EC2 instance type on the launch options page. On the previous screenshot, we use the US East (N. Virginia) region and the EC2 Instance Type named m4.large. To reduce cost, you need to choose the region closest to your location.

When all choices are done, click the Continue to Launch button to proceed.

Setting up a VPC and an EC2 Instance Type

In this demonstration, we use the VPC (virtual private cloud) named

vpc-484bb12f. The exact name of VPC may be different from the example discussed here.


Select VPC in the VPC Settings section.

Instead of a VPC (virtual private cloud) you may choose the EC2 Classic (no VPC) option and use a public cloud.

Selecting a subnet, you effectively choose an availability zone in the selected region. We recommend that you choose the availability zone where your RDS is located.

Note that the cost estimation is automatically updated based on your choice.

Limiting Access to the instance: security group and a key pair

In the Security Group section, which acts like a firewall, you may use the preselected option Create new based on seller settings to create a security group with recommended settings. In the Key Pair select an already set up EC2 key pair to limit access to your instance.


Select an already existing key pair (use the EC2 console to create one if necessary)


It is important that the security group allow communication via the following ports: 22, 80, and 443. PMM should also be able to access port 3306 on the RDS that uses the instance.


Select a security group which manages firewall settings.

Applying settings

Scroll up to the top of the page to view your settings. Then, click the Launch with 1 click button to continue and adjust your settings in the EC2 console.


Your instance settings are summarized in a special area. Click the Launch with 1 click button to continue.


The Launch with 1 click button may alternatively be titled as Accept Software Terms & Launch with 1-Click.

Adjusting instance settings in the EC2 Console

Your clicking the Launch with 1 click button, deploys your instance. To continue setting up your instance, run the EC2 console. It is available as a link at the top of the page that opens after you click the Launch with 1 click button.

Your instance appears in the EC2 console in a table that lists all instances available to you. When a new instance is only created, it has no name. Make sure that you give it a name to distinguish from other instances managed via the EC2 console.


The newly created instance selected.

Running the instance

After you add your new instance it will take some time to initialize it. When the AWS console reports that the instance is now in a running state, you many continue with configuration of PMM Server.


When started the next time after rebooting, your instance may acquire another IP address. You may choose to set up an elastic IP to avoid this problem.

See also

Amazon Documentation: Elastic IP Addresses

With your instance selected, open its IP address in a web browser. The IP address appears in the IPv4 Public IP column or as value of the Public IP field at the top of the Properties panel.


The public IP address of the instance

To run the instance, copy and paste its public IP address to the location bar of your browser. In the Percona Monitoring and Management welcome page that opens, enter the instance ID.


Entering the instance ID when installing PMM Server

You can copy the instance ID from the Properties panel of your instance, select the Description tab back in the EC2 console. Click the Copy button next to the Instance ID field. This button appears as soon as you hover the cursor of your mouse over the ID.


Hover the cursor over the instance ID for the Copy button to appear.

Paste the instance in the Instance ID field of the Percona Monitoring and Management welcome page and click Submit.

Click Submit and enter your user name and password in the dialog window that pops up. The PMM Server is now ready and the home page opens.


Create credentials for your instance.

Click Submit and enter your user name and password in the dialog window that pops up. The PMM Server is now ready and the home page opens.


PMM Server home page

You are creating a username and password that will be used for two purposes:

  1. authentication as a user to PMM - this will be the credentials you need in order to log in to PMM.

  2. authentication between PMM Server and PMM Clients - you will re-use these credentials when configuring pmm-client for the first time on a server, for example:

    Run this command as root or by using the sudo command

    $ pmm-admin config --username= --password= --server=


Accessing the instance by using an SSH client.

For instructions about how to access your instances by using an SSH client, see Connecting to Your Linux Instance Using SSH

Make sure to replace the user name ec2-user used in this document with admin.

See also

How to verify that the PMM Server is running properly?
Verifying PMM Server
How to connect a PMM Client to the PMM Server?
Connecting PMM Clients to the PMM Server

Resizing the EBS Volume

Your instance comes with a predefined size which can become a limitation. To make more disk space available to your instance, you need to increase the size of the EBS volume as needed and then reconfigure your instance to use the new size.

The procedure of resizing EBS volumes is described in the Amazon documentation: Modifying the Size, IOPS, or Type of an EBS Volume on Linux.

As soon as the EBS volume is updated, connect to your instance and update it to use the new size:

Run the following commands as root or by using the sudo command

  1. Detect the type of your filesystem: mount | grep '/srv'

  2. In case of XFS reboot instance or run the following commands:

    $ pvresize /dev/xvdb
    $ lvextend -l '100%VG' /dev/DataVG/ThinPool
    $ lvextend -l '80%VG' /dev/DataVG/DataLV
    $ xfs_growfs -d /srv
  3. In case of btrfs, run the following command:

    $ btrfs filesystem resize max /srv

More information in AWS documentation

Elastic IP Addresses
Amazon EC2 Security Groups for Linux Instances
Connecting to Your Linux Instance Using SSH (use admin as the user name)

Running PMM Server Using Amazon Machine Images

Percona provides public Amazon Machine Images (AMI) with PMM Server in all regions where Amazon Web Services (AWS) is available. You can launch an instance using the web console for the corresponding image:

Region String AMI ID
Asia Pacific (Tokyo) ap-northeast-1 ami-0b820887d64b36019
Asia Pacific (Seoul) ap-northeast-2 ami-05cebe40a1ddb45ca
Asia Pacific (Mumbai) ap-south-1 ami-0c346d83f81036944
Asia Pacific (Singapore) ap-southeast-1 ami-0c745eaf6076ce25a
Asia Pacific (Sydney) ap-southeast-2 ami-06fa23f0e2b8d213a
Canada (Central) ca-central-1 ami-0b917c4a7a0276eac
EU (Frankfurt) eu-central-1 ami-08162b74cd49394ff
EU (Ireland) eu-west-1 ami-0a5a4f0b6a26d5614
EU (London) eu-west-2 ami-0240cb30cd77447b1
EU (Paris) eu-west-3 ami-062de16e2467c48eb
South America (São Paulo) sa-east-1 ami-0dd564a574c06cc0b
US East (N. Virginia) us-east-1 ami-065c25d54dec97e0d
US East (Ohio) us-east-2 ami-0a0a36c5d6d1d7a32
US West (N. California) us-west-1 ami-01850dd8d49567811
US West (Oregon) us-west-2 ami-0c0c430810628b8ee

Running from Command Line

  1. Launch the PMM Server instance using the run-instances command for the corresponding region and image. For example:

    aws ec2 run-instances \
       --image-id ami-30ad0f4d \
       --security-group-ids sg-3b6e5e46 \
       --instance-type t2.micro \
       --subnet-id subnet-4765a930 \
       --region us-east-1 \
       --key-name SSH-KEYNAME


    Providing the public SSH key is optional. Specify it if you want SSH access to PMM Server.

  2. Set a name for the instance using the create-tags command. For example:

    aws ec2 create-tags  \
       --resources i-XXXX-INSTANCE-ID-XXXX \
       --region us-east-1 \
       --tags Key=Name,Value=OWNER_NAME-pmm
  3. Get the IP address for accessing PMM Server from console output using the get-console-output command. For example:

    aws ec2 get-console-output \
       --instance-id i-XXXX-INSTANCE-ID-XXXX \
       --region us-east-1 \
       --output text \
       | grep cloud-init