You can download the Automox agent as an .rpm or .deb package directly from the console and install it locally, rather than using the one-line installer. This is useful when deploying through configuration management, when a host cannot reach the console directly, or when the one-line installer fails on a distribution that rejects the package it retrieves.
Prerequisites
Before you begin, ensure:
- You have an active Automox account and access to the console.
- Your network allows access to the Automox console.
- You have appropriate permissions to download agent packages.
Steps to Download the Linux Package
- Log in to the Automox console.
- Navigate to the Devices tab.
- Click Add Devices.
- From the drop-down menu, select Linux.
- Scroll to the bottom of the pop-up window and click on Manual Installation.
- Choose the package that matches your distribution and architecture. See the table below if you are unsure.
- Download the package to the target device.
Choosing the right package
| Package | Use for |
|---|---|
| .deb | Debian-based distributions, including Debian and Ubuntu |
| .rpm | Red Hat-based distributions, including RHEL, CentOS, Rocky Linux, AlmaLinux and Amazon Linux |
| SUSE .rpm | SUSE Linux Enterprise Server and openSUSE |
SUSE uses its own package. There is a dedicated SUSE build separate from the general Red Hat .rpm, and its file name contains .suse. After downloading, confirm the file name matches the distribution you intend to install on, since the general .rpm and the SUSE .rpm otherwise look similar.
Each package is also published per architecture, so match the architecture of the host as well as the distribution. Confirm your distribution and architecture are supported before deploying, in Linux: Recommendations, Requirements, and FAQs.
Installing the downloaded package
The manual installation page in the console displays the exact commands for the package you selected, including your organization's access key. Follow those commands on the device.
If the agent is installed but the access key was not applied, the service starts and then stops, and the agent log records an authentication failure. Set the key directly and start the service:
sudo /opt/amagent/amagent --setkey ACCESS_KEY sudo systemctl enable amagent sudo systemctl start amagent sudo systemctl status amagent
For confirming the agent is running and healthy afterwards, see Checking and Starting the Automox Agent - Linux.
When to use this instead of the one-line installer
On SUSE, the one-line installer can fail with a signature verification error, because SUSE requires RPM packages to be signed and the installer presents the package to zypper as a plain RPM file. Downloading the SUSE package from the console and installing it locally resolves that case. See Agent Install Failure on SUSE Linux.