This page provides directions for installing, starting, and configuring InfluxDB open source (OSS).

InfluxDB OSS installation requirements

Installation of the InfluxDB package may requireroot or administrator privileges in order to complete successfully.

InfluxDB OSS networking ports

By default, InfluxDB uses the following network ports:

• TCP port8086 is available for client-server communication using the InfluxDB API.
• TCP port8088 is available for the RPC service to perform back up and restore operations.
• TCP port2003 is available for the Graphite protocol (when enabled).

In addition to the ports above, InfluxDB also offers multiple plugins that mayrequirecustom ports.All port mappings can be modified through theconfiguration file,which is located at/etc/influxdb/influxdb.conf for default installations.

Network Time Protocol (NTP)

InfluxDB uses a host’s local time in UTC to assign timestamps to data and forcoordination purposes.Use the Network Time Protocol (NTP) to synchronize time between hosts; if hosts'clocks aren’t synchronized with NTP, the timestamps on the data written to InfluxDBcan be inaccurate.

Installing InfluxDB OSS

For users who don’t want to install any software and are ready to use InfluxDB,you may want to check out ourmanaged hosted InfluxDB offering.

# influxdata-archive.key GPG fingerprint:#   Primary key fingerprint: 24C9 75CB A61A 024E E1B6  3178 7C3D 5715 9FC2 F927#   Subkey fingerprint:      9D53 9D90 D332 8DC7 D6C8  D3B9 D8FF 8E1F 7DF8 B07Ewget -q https://repos.influxdata.com/influxdata-archive.keygpg --show-keys --with-fingerprint --with-colons ./influxdata-archive.key 2>&1| grep -q'^fpr:\+24C975CBA61A024EE1B631787C3D57159FC2F927:$'&& cat influxdata-archive.key| gpg --dearmor| sudo tee /etc/apt/keyrings/influxdata-archive.gpg > /dev/nullecho'deb [signed-by=/etc/apt/keyrings/influxdata-archive.gpg] https://repos.influxdata.com/debian stable main'| sudo tee /etc/apt/sources.list.d/influxdata.list

# influxdata-archive.key GPG fingerprint:#   Primary key fingerprint: 24C9 75CB A61A 024E E1B6  3178 7C3D 5715 9FC2 F927#   Subkey fingerprint:      9D53 9D90 D332 8DC7 D6C8  D3B9 D8FF 8E1F 7DF8 B07Ecurl --silent --location -O https://repos.influxdata.com/influxdata-archive.keygpg --show-keys --with-fingerprint --with-colons ./influxdata-archive.key 2>&1| grep -q'^fpr:\+24C975CBA61A024EE1B631787C3D57159FC2F927:$'&& cat influxdata-archive.key| gpg --dearmor| sudo tee /etc/apt/keyrings/influxdata-archive.gpg > /dev/nullecho'deb [signed-by=/etc/apt/keyrings/influxdata-archive.gpg] https://repos.influxdata.com/debian stable main'| sudo tee /etc/apt/sources.list.d/influxdata.list

sudo apt-get update&& sudo apt-get install influxdbsudo service influxdb start

sudo apt-get update&& sudo apt-get install influxdbsudo systemctl unmask influxdb.servicesudo systemctl start influxdb

cat<<EOF | sudo tee /etc/yum.repos.d/influxdb.repo[influxdb]name = InfluxDB Repository - RHEL \$releaseverbaseurl = https://repos.influxdata.com/rhel/\$releasever/\$basearch/stableenabled = 1gpgcheck = 1gpgkey = https://repos.influxdata.com/influxdata-archive.keyEOF

sudo yum install influxdbsudo service influxdb start

sudo yum install influxdbsudo systemctl start influxdb

# add go repositoryzypper ar -f obs://devel:languages:go/ go# install latest influxdbzypper in influxdb

sudo pkg install influxdb

sudo service influxd onestart

brew updatebrew install influxdb@1

$ /usr/local/opt/influxdb/bin/influxd versionInfluxDB 1.12.2(git: none) build_date: 2021-04-01T17:55:08Z$ /usr/local/opt/influxdb@1/bin/influxd versionInfluxDB v(git: unknown unknown)

# Pull the latest InfluxDB v1.x imagedocker pull influxdb:1.12.2# Start InfluxDB with persistent storagedocker run -p 8086:8086\  -v$PWD/data:/var/lib/influxdb\  influxdb:1.12.2

Verify the authenticity of downloaded binary (optional)

For added security, follow these steps to verify the signature of your InfluxDB download withgpg.

(Most operating systems include thegpg command by default.Ifgpg is not available, see theGnuPG homepage for installation instructions.)

1. Download and import InfluxData’s public key:

   curl -s https://repos.influxdata.com/influxdata-archive.key | gpg --import

2. Download the signature file for the release by adding.asc to the download URL.For example:

   wget https://download.influxdata.com/influxdb/releases/influxdb-1.12.2-linux-amd64.tar.gz.asc

3. Verify the signature withgpg --verify:

   gpg --verify influxdb-1.12.2_linux_amd64.tar.gz.asc influxdb-1.12.2-linux-amd64.tar.gz

   The output from this command should include the following:

   gpg: Good signature from "InfluxData Package Signing Key <support@influxdata.com>" [unknown]

Configuring InfluxDB OSS

The system has internal defaults for every configuration file setting.View the default configuration settings with theinfluxd config command.

Most of the settings in the local configuration file(/etc/influxdb/influxdb.conf) are commented out; allcommented-out settings will be determined by the internal defaults.Any uncommented settings in the local configuration file override theinternal defaults.Note that the local configuration file does not need to include everyconfiguration setting.

There are two ways to launch InfluxDB with your configuration file:

• Point the process to the correct configuration file by using the-configoption:

  influxd -config /etc/influxdb/influxdb.conf

• Set the environment variableINFLUXDB_CONFIG_PATH to the path of yourconfiguration file and start the process.For example:

  echo $INFLUXDB_CONFIG_PATH/etc/influxdb/influxdb.confinfluxd

InfluxDB first checks for the-config option and then for the environmentvariable.

Configuring InfluxDB with Docker

For detailed Docker configuration instructions including environment variables, configuration files, initialization options, and examples, see:

Install and run with Docker ›

See theConfiguration documentation for more information.

Data and WAL directory permissions

Make sure the directories in which data and thewrite ahead log (WAL) are stored are writable for the user running theinfluxd service.

The user running theinfluxd process should have the following permissions fordirectories in theInfluxDB file system:

Information aboutdata andwal directory paths is available in theData settings section of theConfiguring InfluxDB documentation.

Hosting InfluxDB OSS on AWS

Hardware requirements for InfluxDB

We recommend using two SSD volumes, using one for theinfluxdb/wal and the other for theinfluxdb/data.Depending on your load, each volume should have around 1k-3k provisioned IOPS.Theinfluxdb/data volume should have more disk space with lower IOPS and theinfluxdb/wal volume should have less disk space with higher IOPS.

Each machine should have a minimum of 8GB RAM.

We’ve seen the best performance with the R4 class of machines, as they provide more memory than either of the C3/C4 class and the M4 class.

Configuring InfluxDB OSS instances

This example assumes that you are using two SSD volumes and that you have mounted them appropriately.This example also assumes that each of those volumes is mounted at/mnt/influx and/mnt/db.For more information on how to do that see the Amazon documentation on how toAdd a Volume to Your Instance.

Configuration file

You’ll have to update the configuration file appropriately for each InfluxDB instance you have.

...[meta]dir="/mnt/db/meta"......[data]dir="/mnt/db/data"...wal-dir="/mnt/influx/wal"......[hinted-handoff]...dir="/mnt/db/hh"...

Authentication and Authorization

For all AWS deployments, we strongly recommend authentication be enabled. Without this, it is possible that your InfluxDBinstance may be publicly available to any unauthenticated user. The default settings doNOT enableauthentication and authorization. Further, authentication and authorization should not be solely relied upon to prevent accessand protect data from malicious actors. If additional security or compliance features are desired, InfluxDB should be runbehind additional services offered by AWS.Review theauthentication and authorization settings.

InfluxDB OSS permissions

When using non-standard directories for InfluxDB data and configurations, also be sure to set filesystem permissions correctly:

chown influxdb:influxdb /mnt/influxchown influxdb:influxdb /mnt/db

For InfluxDB 1.7.6 or later, you must give owner permissions to theinit.sh file. To do this, run the following script in yourinfluxdb directory:

if[ ! -f"$STDOUT"];then    mkdir -p$(dirname$STDOUT)    chown$USER:$GROUP$(dirname$STDOUT)fiif[ ! -f"$STDERR"];then    mkdir -p$(dirname$STDERR)    chown$USER:$GROUP$(dirname$STDERR)fi# Override init script variables with DEFAULT values