One binary. Polls the Collector over outbound HTTPS. Same steps the dashboard shows under /clm/agent-setup.
The TigerTrust Agent is the only thing you install on a host to bring it under CLM management. It never listens on any port; it dials out to the Collector on 443 and pulls work.
This page mirrors the Agent Setup wizard in the dashboard (/clm/agent-setup). Copy commands from either side — they’re identical.
The script detects your distro, adds the right package repo, installs tigertrust-agent, writes /etc/tigertrust-agent/config.yaml, and enables the systemd service.
2
Verify
sudo systemctl status tigertrust-agent
The host appears in Infrastructure → Agents within 30 seconds of first heartbeat.
Every distro-specific flow above is what the single install.sh runs internally. It’s fetched from https://releases.tigertrust.io/tigertrust-agent/scripts/install.sh and:
Detects the platform (/etc/os-release, uname -m).
On Debian/Ubuntu, imports the GPG key and adds the apt source; on RHEL/CentOS, drops the .repo file.
Installs the tigertrust-agent package.
Runs tigertrust-agent configure with the flags you passed on the curl line.
Enables and starts the systemd service.
Supported flags:
--collector-url <url> (required)--api-key <key> (required)--agent-name <name> optional; defaults to hostname--config <path> optional; use a pre-written config file--channel <stable|beta> optional; default: stable
Agents advertise what they support. A discovery-only agent claims different capabilities than a data-center agent that also deploys certs. Edit /etc/tigertrust-agent/config.yaml and restart:
The control plane only schedules tasks the agent claims to support, so a stripped-down IoT agent (discovery + renewal only) can coexist with full-featured hosts in the same workspace.