influxctl management create

Limited availability

InfluxDB Clustered is currently 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.

The influxctl management create command creates a management token to be used with an InfluxDB cluster. Management tokens authorize a user to perform administrative tasks on the InfluxDB instance such as creating and deleting databases, managing users, and other administrative tasks.

Management tokens do not provide access to databases or data in databases. Only database tokens with “read” or “write” permissions can access data in databases.

The optional --expires-at flag defines the token expiration date and time. Provide an RFC3999 date string–for example: 2024-05-29T00:00:00Z. If not set, the token does not expire until revoked.

The --format flag lets you print the output in other formats. The json format is available for programmatic parsing by other tooling. Default: table.

Store secure tokens in a secret store

Management token strings are returned only on token creation. We recommend storing management tokens in a secure secret store.


influxctl management create [flags]


Flag Description
--description Management token description
--expires-at Token expiration date
--format Output format (table (default) or json)
-h --help Output command help


Create a management token with no expiration

influxctl management create

Create a management token with an expiration and description

influxctl management create \
--description "

Replace the following:

  • RFC3339_EXPIRATION: An RFC3339 date string to expire the token at–for example: 2024-05-29T00:00:00Z.
  • TOKEN_DESCRIPTION: Management token description.

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: