How to install nginx-amplify-agent (x86_64)

GetPageSpeed Amplify Agent

License: 2-clause BSD-like license Vendor: GetPageSpeed https://github.com/GetPageSpeed/nginx-amplify-agent

Install

sudo yum -y install https://extras.getpagespeed.com/release-latest.rpm
sudo yum -y install nginx-amplify-agent

Description

The GetPageSpeed Amplify Agent is a small, Python application that provides system and NGINX metric collection. It is part of GetPageSpeed Amplify - the monitoring and configuration assistance service for NGINX. This package installs and runs GetPageSpeed Amplify Agent daemon. See https://amplify.getpagespeed.com for more information

RPMs

nginx-amplify-agent-1.8.15-1.amzn2023.x86_64 [3.5 MiB]

GetPageSpeed (2026-05-28) — - 1.8.15-1 · - Fix `yum upgrade`/`apt upgrade` not restarting the agent. The %post/postinst · upgrade branch detected the running agent with `pgrep amplify-agent`, which · matches only the process comm -- truncated by the kernel to 15 chars · (`nginx-amplify-a`), so the pattern `amplify-agent` never matched and the · stop/start was skipped, leaving old code resident. Use · `pgrep -f nginx-amplify-agent.py`, which matches the full process cmdline.

nginx-amplify-agent-1.8.14-1.amzn2023.x86_64 [3.5 MiB]

GetPageSpeed (2026-05-28) — - 1.8.14-1 · - Close a restart-recovery hole. An uncaught exception during agent startup · (notably the initial talk_to_cloud raising AmplifyCriticalException when a · rapid restart races the cloud handshake) was logged and then let the process · fall off the end of run() and exit 0. systemd Restart=on-failure treats a · clean exit as success, so the agent stayed inactive (dead) instead of being · revived; a single manual start recovered it. main.run() now exits non-zero on · any uncaught run-time exception, so the existing on-failure net (1.8.12-1) · restarts it -- and the fresh process re-runs gevent.reinit() (1.8.11-1). · - Stop two destructors (AbstractManager.__del__, FileTail.__del__) from raising · during garbage collection / interpreter shutdown -- a missing `running` · attribute and a None context.log surfaced as unraisable-exception warnings.

nginx-amplify-agent-1.8.13-1.amzn2023.x86_64 [3.5 MiB]

GetPageSpeed (2026-05-27) — - 1.8.13-1 · - Stop the recurring "workers_io raised AccessDenied" log noise. The NGINX · worker IO collector reads /proc//io, which is ptrace-gated and · unreadable for the root-owned master (and even between same-user workers), · so io_counters() raised psutil.AccessDenied and aborted the whole collection · cycle, zeroing nginx.workers.io.kbs_r/kbs_w. Now skip the inaccessible · process and sum IO over the readable workers. NoSuchProcess still propagates · to the need_restart path.

nginx-amplify-agent-1.8.12-1.amzn2023.x86_64 [3.5 MiB]

GetPageSpeed (2026-05-27) — - 1.8.12-1 · - systemd auto-restart safety net for the cold-boot start path. The · gevent.reinit() fix in 1.8.11-1 is the cure for the EL7 fork race; this · guarantees recovery if it ever loses the race on some cold-boot FD timing. · Adds Restart=on-failure, RestartSec=5s, StartLimitInterval=60, · StartLimitBurst=3 to the unit (pre-v230 names in [Service] for EL7 · systemd 219). on-failure does not fight a clean `systemctl stop`; the · bounded limit lets a transient boot race recover on retry yet still · surfaces a persistent failure as `failed` instead of looping forever.

nginx-amplify-agent-1.8.11-1.amzn2023.x86_64 [3.5 MiB]

GetPageSpeed (2026-05-22) — - 1.8.11-1 · - Fix "This operation would block forever" race on EL7 cold-boot start. · python-daemon's DaemonContext double-forks via os.fork captured at · import time -- before our gevent.monkey.patch_all() ran -- so gevent's · auto-reinit-on-fork never fires. The child process inherited a hub · whose libev wakefd/eventfd were closed during fork, and the · supervisor's first network call raised · gevent.hub.LoopExit("This operation would block forever"). · Call gevent.reinit() in the child immediately after DaemonContext · enters to rebuild the libev hub. Manifested at cold boot on EL7; · warm restarts got scattered FD numbers and usually escaped the race.

nginx-amplify-agent-1.8.10-1.amzn2023.x86_64 [3.5 MiB]

GetPageSpeed (2026-05-19) — - 1.8.10-1 · - (DEB-only fix, no behavior change on RPM.) Follow-up to 1.8.9-1 · after the test-deb-reinstall-recovery integration test caught two · more bugs on jammy: · * override_dh_installdeb in debian/rules strips agent.conf.default · from the auto-detected conffiles list. The 1.8.9-1 attempt used a · .conffiles file, but that APPENDS to auto-detection rather than · replacing it. · * postinst no longer early-exits on the upgrade branch when · agent.conf is missing -- the early exit was skipping · dh_installsystemd's unmask, so a service masked by `apt-get remove` · stayed masked through reinstall and install.sh's "Launching" step · failed. · - (Cross-distro) install.sh self-heal branch added in 1.8.9-1 has been · removed -- redundant once 1.8.10-1 is the latest available package.

nginx-amplify-agent-1.8.9-1.amzn2023.x86_64 [3.5 MiB]

GetPageSpeed (2026-05-19) — - 1.8.9-1 · - install.sh self-heals a missing /etc/amplify-agent/agent.conf.default · after package install (yum reinstall on RPM, apt-get install --reinstall · --force-confmiss on DEB). Closes a customer-reported "can't find · /etc/amplify-agent/agent.conf.default" abort on Ubuntu 22.04 after a · remove + rm /etc/amplify-agent + reinstall cycle. · - DEB-only: agent.conf.default is no longer registered as a dpkg conffile · (it is a build-time template for install.sh, not a user-editable config). · No behavior change on RPM, since the spec lists /etc/amplify-agent//* without · %config(noreplace).

nginx-amplify-agent-1.8.8-1.amzn2023.x86_64 [3.5 MiB]

GetPageSpeed (2026-05-16) — - 1.8.5-2 · - Fix TypeError in exponential_delay() on Python 3.12+ (Noble/Trixie/EL10/Fedora/SLES16) · - Ported from upstream PR github.com/nginxinc/nginx-amplify-agent/pull/125 by @jasil1414

nginx-amplify-agent-1.8.7-1.amzn2023.x86_64 [3.5 MiB]

nginx-amplify-agent-1.8.6-1.amzn2023.x86_64 [3.5 MiB]

nginx-amplify-agent-1.8.5-2.amzn2023.x86_64 [3.4 MiB]

nginx-amplify-agent-1.8.5-1.amzn2023.x86_64 [3.4 MiB]

GetPageSpeed (2026-05-14) — - 1.8.5-1 · - Agent now starts when agent.conf lacks the optional [loggers]/[handlers]/[formatters] sections (falls back to built-in logging defaults) · - systemd unit Documentation URL points to amplify.getpagespeed.com/docs

nginx-amplify-agent-1.8.4-8.amzn2023.x86_64 [3.5 MiB]