Managing security in InfluxDB Enterprise

Some customers may choose to install InfluxDB Enterprise 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 Enterprise instance.

Enabling authentication

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

Resources: Set up Authentication

Managing 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, Fine-grained authorization

Enabling HTTPS

Using HTTPS secures the communication between clients and the InfluxDB server, and, in some cases, HTTPS verifies the authenticity of the InfluxDB server to clients (bi-directional authentication). The communicatio between the meta nodes and the data nodes are also secured via HTTPS.

Resources: Enabling HTTPS

Secure your Host

Ports

For InfluxDB Enterprise Data Nodes, close all ports on each host except for port 8086. You can also use a proxy to port 8086. By default, data nodes and meta nodes communicate with each other over ‘8088’,‘8089’,and’8091’

For InfluxDB Enterprise, backuping and restoring is performed from the meta nodes.

AWS Recommendations

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

This documentation is open source. See a typo? Please, open an issue.


Need help getting up and running? Get Support