AegisOne

Agent deployment

Installing on Linux

Root install, service registration, and deploying across many hosts at once.

Last updated

The Linux agent is a single static binary. Download it, make it executable, and run the install subcommand as root with your token and console host.

bash
SERVER="https://<your-console-host>"
TOKEN="<INSTALL_TOKEN>"

curl -fsSL "$SERVER/api/agents/download/linux" -o /tmp/aegisone-agent
chmod +x /tmp/aegisone-agent
sudo /tmp/aegisone-agent install --token "$TOKEN" --server "$SERVER"

The install registers a service under the host init system so the agent starts at boot. Verify it before moving on.

bash
systemctl status aegisone-agent --no-pager
journalctl -u aegisone-agent -n 50 --no-pager

For multiple hosts, drive the same three commands over your existing remote-execution path. The install is idempotent enough to re-run safely on a host that is already enrolled, but re-running with a different token is not a supported way to move an endpoint between clients — reassign it in the console instead.

bash
# Simple fan-out over a host list, if you have nothing more sophisticated to hand
while read -r host; do
  ssh "$host" "curl -fsSL $SERVER/api/agents/download/linux -o /tmp/aegisone-agent \
    && chmod +x /tmp/aegisone-agent \
    && sudo /tmp/aegisone-agent install --token '$TOKEN' --server '$SERVER'" \
    && echo "OK   $host" || echo "FAIL $host"
done < hosts.txt

That loop deliberately prints a per-host result rather than aborting on first failure. In any real estate a handful of hosts will be unreachable, mid-reboot, or out of disk, and you want the list of which ones rather than a run that stopped at the third entry.

If your hosts reach the internet through a proxy, make sure the proxy environment is present for the service and not only for your interactive shell. An install that works when you run it by hand and fails as a service is nearly always this.