influx config create

The influx config create command creates a InfluxDB connection configuration and stores it in a local file:

OS/PlatformCLI config file path
Linux (installed as binary)~/.influxdbv2/configs
Linux (installed as service)~/var/lib/influxdb/configs
Docker (DockerHub)/etc/influxdb2/configs
Docker (

To view CLI connection configurations after creating them, use influx config list.

Note: If you create multiple connection configurations (for example, separate admin and user configurations), use influx config <config-name> to switch to the configuration you want to use.


influx config create [flags]


FlagDescriptionInput typeMaps to ?
-a--activeSet the specified connection to be the active configuration.
-n--config-name(Required) Name of the new configuration.string
-h--helpHelp for the create command
--hide-headersHide table headers (default false)INFLUX_HIDE_HEADERS
-u--host-url(Required) Connection URL for the new configuration.string
--jsonOutput data as JSON (default false)INFLUX_OUTPUT_JSON
-o--orgOrganization namestring
-t--tokenAPI tokenstringINFLUX_TOKEN
-p--username-password(OSS only) Username (and optionally password) to use for authentication.
Include username:password to ensure a session is automatically authenticated. Include username (without password) to prompt for a password before creating the session.string


Create a connection configuration and set it active

influx config create --active \
  -n config-name \
  -u http://localhost:8086 \
  -t mySuP3rS3cr3tT0keN \
  -o example-org

Create a connection configuration without setting it active

influx config create \
  -n config-name \
  -u http://localhost:8086 \
  -t mySuP3rS3cr3tT0keN \
  -o example-org

Was this page helpful?

Thank you for your feedback!

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:

InfluxDB Cloud powered by TSM