This is archived documentation for InfluxData product versions that are no longer maintained. For newer documentation, see the latest InfluxData documentation.
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.
Password protect your InfluxDB instance to keep any unauthorized individuals from accessing you data.
Resources: Set up Authentication
Manage Users and their Permissions
Restrict access by creating individual users and assigning them relevant read and/or write permissions.
Set up 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).
Resources: HTTPS Setup
Secure your Host
If you’re only running InfluxDB, close all ports on the host except for port
You can also use a proxy to port
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.
We recommend implementing on-disk encryption; InfluxDB does not offer built-in support to encrypt the data.