Manage InfluxDB security

This page documents an earlier version of InfluxDB. InfluxDB v2 is the latest stable version. See the equivalent InfluxDB v2 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.

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: