Documentation

Install InfluxDB 3 Enterprise

Upgrading from InfluxDB 3 Core?

If you’re currently running InfluxDB 3 Core and want to upgrade to InfluxDB 3 Enterprise, see Upgrade from Core for step-by-step instructions.

Multi-node cluster setup

For information about setting up a multi-node InfluxDB 3 Enterprise cluster, see Create a multi-node cluster in the Get started guide.

For steps to upgrade an existing InfluxDB 3 Enterprise cluster, see Upgrade InfluxDB.

System Requirements

Operating system

InfluxDB 3 Enterprise runs on Linux, macOS, and Windows.

Object storage

A key feature of InfluxDB 3 is its use of object storage to store time series data in Apache Parquet format. You can choose to store these files on your local file system. Performance on your local filesystem will likely be better, but object storage has the advantage of not running out of space and being accessible by other systems over the network. InfluxDB 3 Enterprise natively supports Amazon S3, Azure Blob Storage, and Google Cloud Storage. You can also use many local object storage implementations that provide an S3-compatible API, such as Minio.

Install

InfluxDB 3 Enterprise runs on Linux, macOS, and Windows.

Choose one of the following methods to install InfluxDB 3 Enterprise:

Quick install for Linux and macOS

To install InfluxDB 3 Enterprise on Linux or macOS, download and run the quick installer script for InfluxDB 3 Enterprise–for example, using curl to download the script:

curl -O https://www.influxdata.com/d/install_influxdb3.sh \
&& sh install_influxdb3.sh enterprise

The quick installer script is updated with each InfluxDB 3 Enterprise release, so it always installs the latest version.

Production deployment

For production deployments, use Linux DEB or RPM for built-in systemd sandboxing, or Docker with your own container security configuration.

For detailed security options, see Manage security.

Download and install the latest build artifacts

You can also download and install InfluxDB 3 Enterprise build artifacts directly:

macOS binaries

Pull the Docker image

Run the following command to pull the influxdb:3-enterprise image, available for x86_64 (AMD64) and ARM64 architectures:

docker pull influxdb:3-enterprise

Docker automatically pulls the appropriate image for your system architecture.

Pull for a specific system architecture

Linux DEB or RPM

When installed via DEB or RPM on a systemd-enabled system, InfluxDB 3 Enterprise runs in a sandboxed environment. The included systemd unit file configures the environment to provide security isolation for typical deployments. For more information, see Manage security.

DEB and RPM installation is recommended for non-Docker production deployments due to built-in systemd sandboxing.

DEB-based systems

RPM-based systems

TOML configuration (Linux)

After you install the DEB or RPM package, the InfluxDB 3 Enterprise TOML configuration file is located at /etc/influxdb3/influxdb3-enterprise.conf and contains the following settings:

License required

InfluxDB 3 Enterprise requires an active license to start. See how to Activate a license.

Run as a system service (Linux)

InfluxDB 3 Enterprise DEB and RPM installs include service files for running as a managed system service on Linux:

  • systemd: For modern Linux distributions
  • SysV init: For legacy system compatibility
Run using systemd

On systemd systems, the influxdb3-enterprise unit file is enabled on install, but the unit is not started in order to allow configuration.

Start, stop, and restart

The following examples use sudo for systems that require elevated privileges. On some systems (such as Amazon Linux or other RHEL-based distributions where you may already be running as root), you can omit sudo from the commands.

# Start the service
sudo systemctl start influxdb3-enterprise

# Stop the service
sudo systemctl stop influxdb3-enterprise

# Restart the service (use after configuration changes)
sudo systemctl restart influxdb3-enterprise
Check status and logs
# Check status (sudo to ensure full journal output)
sudo systemctl status influxdb3-enterprise

# Quick state checks (no sudo needed)
systemctl is-enabled influxdb3-enterprise
systemctl is-active  influxdb3-enterprise

# Recent logs
sudo journalctl --unit influxdb3-enterprise -n 200 --no-pager

# Follow logs
sudo journalctl --unit influxdb3-enterprise -f
Inspect the packaged unit

The packaged unit configures security sandboxing for typical deployments (see Manage security). To inspect the packaged unit and its resolved properties:

# Show the unit file
systemctl cat influxdb3-enterprise

# Show all resolved properties (paths, environment, sandboxing options)
systemctl show influxdb3-enterprise
Apply configuration changes

Edit the TOML configuration file and restart the service to apply changes:

sudoedit /etc/influxdb3/influxdb3-enterprise.conf
sudo systemctl restart influxdb3-enterprise
sudo systemctl status  influxdb3-enterprise
sudo journalctl --unit influxdb3-enterprise -n 100 --no-pager

influxdb3 serve does not support configuration reload; a restart is required after editing the TOML file or changing environment variables.

The TOML file is read by the systemd launcher and converted to INFLUXDB3_* environment variables before influxdb3 serve runs; CLI flags still override values from the TOML file. For details, see TOML configuration files.

Run using SysV

On SysV init systems, influxdb3-enterprise is disabled on install and can be enabled by adjusting /etc/default/influxdb3-enterprise to contain ENABLED=yes.

To start the database, enter the following commands:

# Start the database
/etc/init.d/influxdb3-enterprise start

# View status
/etc/init.d/influxdb3-enterprise status

# View logs
tail -f /var/lib/influxdb3/influxdb3-enterprise.log

Verify the installation

After installing InfluxDB 3 Enterprise, enter the following command to verify that it installed successfully:

influxdb3 --version

If your system can’t locate influxdb3 following a quick install, source the configuration file (for example, .bashrc, .zshrc) for your shell–for example:

source ~/.zshrc

For information about setting up a multi-node InfluxDB 3 Enterprise cluster, see Create a multi-node cluster in the Get started guide.


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2