Install FleetAMP
Use the latest stable release artifact for production-like evaluation. Build from source only when developing FleetAMP.
Choose a deployment model
| Platform | Recommended use | Continue with |
|---|---|---|
| Linux systemd | Single server, VM, or controlled host installation | Operating-system deployment |
| Container or Docker Compose | Local evaluation and demonstrations | Container lab |
| Kubernetes | Isolated lab or platform-managed deployment | Install the image and persistent storage, then connect a Kubernetes gateway |
| Source build | FleetAMP development and contribution | Build from source |
Common requirements
- Linux amd64 or arm64 for packaged server deployment;
- persistent storage for the FleetAMP database;
- network access from Collectors to the OpAMP endpoint;
- a protected HTTP endpoint for the UI and API;
- TLS and authentication for any non-local exposure;
- Node.js 20 or later only for local documentation or frontend development.
Download and verify
- Open the FleetAMP releases page.
- Select the latest stable release.
- Download the artifact for the target platform.
- Verify its published checksum.
- Read the release notes for platform requirements, migrations, and known limitations.
Configure the service
Configure persistent data, the database path, HTTP and OpAMP listeners, TLS, authentication, logging, and any optional integrations. Use a dedicated service identity and restrict file permissions.
For Linux systemd:
sudo systemctl enable --now fleetamp
sudo systemctl status fleetamp
sudo journalctl -u fleetamp -f
Complete first-time setup
- Open the configured FleetAMP URL.
- Follow the first-administrator setup flow.
- Store recovery material securely.
- Sign in and change the bootstrap password if required.
- Create additional users and roles from the administrator area.
- Do not share an administrator account with routine Group Owners.
Verify
Confirm the health and readiness endpoints, sign in to the UI, and review logs before connecting Collectors. Then follow Connect an OTel Collector.
Do not expose an unauthenticated management API or plaintext OpAMP endpoint outside an isolated lab. Apply Transport security and Security hardening.
Upgrade
Back up the database and configuration, read the target release notes, test the upgrade using a copy, run required migrations once, restart, and verify identity, groups, approvals, deployments, integrations, and audit history. Version-specific upgrade boundaries remain in Version history.