Manage InfluxDB security

See the equivalent InfluxDB v2.0 documentation: Manage security and authorization.

Some customers may choose to install InfluxDB with public internet access, however doing so can inadvertently expose your data and invite unwelcome attacks on your database. Check out the sections below for how protect the data in your InfluxDB instance.

Enable authentication

Password protect your InfluxDB instance to keep any unauthorized individuals from accessing your data.

Resources: Set up Authentication

Manage users and permissions

Restrict access by creating individual users and assigning them relevant read and/or write permissions.

Resources: User Types and Privileges, User Management Commands

Enable HTTPS

Enabling HTTPS encrypts the communication between clients and the InfluxDB server. HTTPS can also verify the authenticity of the InfluxDB server to connecting clients.

Resources: Enabling HTTPS

Configure security headers

HTTP headers allow servers and clients to pass additional information along with requests. Certain headers help enforce security properties.

Resources: Configure HTTP headers

Secure your host


If you’re only running InfluxDB, close all ports on the host except for port 8086. You can also use a proxy to port 8086.

InfluxDB uses port 8088 for remote backups and restores. We highly recommend closing that port and, if performing a remote backup, giving specific permission only to the remote machine.

AWS recommendations

We recommend implementing on-disk encryption; InfluxDB does not offer built-in support to encrypt the data.

New! Cloud or OSS?

InfluxDB OSS 2.0 release candidate

InfluxDB OSS v2.0.rc includes breaking changes that require a manual upgrade from all alpha and beta versions. For information, see:

Upgrade to InfluxDB OSS v2.0.rc