InfluxDB database secrets engine
Note: This engine can use external X.509 certificates as part of TLS or signature validation. Verifying signatures against X.509 certificates that use SHA-1 is deprecated and is no longer usable without a workaround starting in Vault 1.12. See the deprecation FAQ for more information.
InfluxDB is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the InfluxDB database.
See the database secrets engine docs for more information about setting up the database secrets engine.
Capabilities
Plugin Name | Root Credential Rotation | Dynamic Roles | Static Roles | Username Customization |
---|---|---|---|---|
influxdb-database-plugin | Yes | Yes | Yes (1.6+) | Yes (1.8+) |
Setup
Enable the database secrets engine if it is not already enabled:
By default, the secrets engine will enable at the name of the engine. To enable the secrets engine at a different path, use the
-path
argument.Configure Vault with the proper plugin and connection information:
Configure a role that maps a name in Vault to an SQL statement to execute to create the database credential:
Usage
After the secrets engine is configured and a user/machine has a Vault token with the proper permission, it can generate credentials.
Generate a new credential by reading from the
/creds
endpoint with the name of the role:
API
The full list of configurable options can be seen in the InfluxDB database plugin API page.
For more information on the database secrets engine's HTTP API please see the Database secret secrets engine API page.