Documentation

influx config create

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

OS/Platform CLI config file path
macOS ~/.influxdbv2/configs
Linux (installed as binary) ~/.influxdbv2/configs
Linux (installed as service) ~/var/lib/influxdb/configs
Windows %USERPROFILE%\.influxdbv2\configs
Docker (DockerHub) /etc/influxdb2/configs
Docker (Quay.io) /root/.influxdbv2/configs
Kubernetes /etc/influxdb2/configs

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.

Usage

influx config create [flags]

Flags

Flag Description Input type Maps to ?
-a --active Set the specified connection to be the active configuration.
-n --config-name (Required) Name of the new configuration. string
-h --help Help for the create command
--hide-headers Hide table headers (default false) INFLUX_HIDE_HEADERS
-u --host-url (Required) Connection URL for the new configuration. string
--json Output data as JSON (default false) INFLUX_OUTPUT_JSON
-o --org Organization name string
-t --token API token string INFLUX_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

Examples

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

Create a connection configuration that uses a username and password

The influx CLI 2.4.0+ lets you create connection configurations that authenticate with InfluxDB OSS 2.4+ using the username and password combination that you would use to log into the InfluxDB user interface (UI). The CLI retrieves a session cookie and stores it, unencrypted, in your configs path.

Use the --username-password, -p option to provide your username and password using the <username>:<password> syntax. If no password is provided, the CLI will prompt for a password after each command that requires authentication.

influx config create \
  -n config-name \
  -u http://localhost:8086 \
  -p example-user:example-password \
  -o example-org

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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.