Upgrade PMM Server on AWS¶

Keep your PMM Server up to date with the latest features, security patches, and performance improvements.

Prerequisites¶

Before upgrading your PMM Server, ensure you have:

a current backup of your PMM data volume
scheduled maintenance window for potential downtime

Upgrade process¶

To upgrade PMM Server on AWS:

Create a backup snapshot of your PMM data volume:

aws ec2 create-snapshot --volume-id vol-xxxxxxxxx --description "Pre-upgrade backup $(date)"

Connect to your PMM Server instance via SSH using the admin user.

Update the PMM Server image in the environment file. Replace X.Y.Z with your target version:

sed -i "s|PMM_IMAGE=.*|PMM_IMAGE=docker.io/percona/pmm-server:X.Y.Z|g" ~/.config/systemd/user/pmm-server.env

Pull the new image, then restart PMM Server. The && operators stop the commands if the pull fails, so PMM Server keeps running the current version:
```
source ~/.config/systemd/user/pmm-server.env && \
podman pull "${PMM_IMAGE}" && \
systemctl --user restart pmm-server
```

Post-upgrade tasks¶

After upgrading PMM Server:

Go to All dashboards > PMM Health > PMM Health and check that all services are running.
Go to Inventory > Services and verify that all monitored nodes and services are listed, their status is Up.
Test monitoring functionality to ensure data collection continues normally.

Rollback procedure¶

If issues occur after upgrade:

Stop the new PMM container:
```
systemctl --user stop pmm-server
```
Restore using your pre-upgrade snapshot. Create a volume from the snapshot, attach it to the instance, and start the previous PMM version.

Troubleshooting upgrades¶

If the container won’t start after the upgrade:

# Check container logs
podman logs pmm-server

# Check systemd service logs
journalctl -u pmm-server.service

# Verify volume mounts
podman inspect pmm-server