Installing Fleet

The Fleet application is distributed as a single static binary. This binary serves:

The Fleet web interface
The Fleet application API endpoints
The osquery TLS server API endpoints

All of these are served via a built-in HTTP server, so there is no need for complex web server configurations. Once you've installed the fleet binary and it's infrastructure dependencies as illustrated below, refer to the Configuring The Fleet Binary documentation for information on how to use and configure the Fleet application.

Fleet Quickstart

Kolide provides a quickstart script that is the quickest way to get a demo Fleet instance up and running. Note that the quickstart is not intended to be a production deployment. If you would like a production deployment, please choose one of the methods below.

Installing the Fleet binary

Because everyone's infrastructure is different, there are a multiple options available for installing the Fleet binary.

Docker container

Pull the latest Fleet docker image:

docker pull kolide/fleet

For more information on using Fleet, refer to the Configuring The Fleet Binary documentation.

Raw binaries

Download the latest raw Fleet binaries:

curl -O https://dl.kolide.co/bin/fleet_latest.zip

Unzip the binaries for your platform:

# For a Darwin compatible binary
unzip fleet_latest.zip 'darwin/*' -d fleet
./fleet/darwin/fleet_darwin_amd64 --help

# For a Linux compatible binary
unzip fleet_latest.zip 'linux/*' -d fleet
./fleet/linux/fleet_linux_amd64 --help

For more information on using Fleet, refer to the Configuring The Fleet Binary documentation.

Infrastructure Dependencies

Fleet currently has two infrastructure dependencies in addition to the fleet web server itself. Those dependencies are MySQL and Redis.

MySQL

Fleet uses MySQL extensively as it's main database. Many cloud providers (such as AWS and GCP) host reliable MySQL services which you may consider for this purpose. A well supported MySQL Docker container also exists if you would rather run MySQL in a container. For more information on how to configure the fleet binary to use the correct MySQL instance, see the Configuring The Fleet Binary document.

Redis

Fleet uses Redis to ingest and queue the results of distributed queries, cache data, etc. Many cloud providers (such as AWS and GCP) host reliable Redis services which you may consider for this purpose. A well supported Redis Docker container also exists if you would rather run Redis in a container. For more information on how to configure the fleet binary to use the correct Redis instance, see the Configuring The Fleet Binary document.

3.1 KiB Raw Blame History