Documentation

InfluxDB 3 Cloud

Set up InfluxDB 3 Cloud

InfluxDB 3 Cloud is the fully managed, cloud-hosted version of InfluxDB 3 Enterprise. InfluxData provisions and operates the InfluxDB 3 servers for you, so you don’t install, run, or scale servers yourself. To get started, get your instance host from InfluxData, configure the influxdb3 CLI, log in, and then create a database.

Get your instance

During early access, InfluxData provisions InfluxDB 3 Cloud instances for you. You can’t sign up for the service yourself. To request early access, see the InfluxDB 3 Cloud product page.

After your instance is provisioned, InfluxData provides your instance host URL, which is the endpoint you connect to. You authenticate with your InfluxData account in the following steps. You don’t copy or store a token for interactive use.

Configure the influxdb3 CLI

The influxdb3 CLI lets you administer your instance and write and query data from the command line. Because InfluxDB 3 Cloud is fully managed, you don’t install or run anything for the service itself. You point the influxdb3 CLI at your hosted instance and log in with your InfluxData account.

Connect to your instance

Set the INFLUXDB3_HOST_URL environment variable for the influxdb3 CLI to connect to your instance host URL:

macOS and Linux PowerShell CMD

export INFLUXDB3_HOST_URL=https://instance-id.enterprise.influxdb.io
$env:INFLUXDB3_HOST_URL = "https://instance-id.enterprise.influxdb.io"
set INFLUXDB3_HOST_URL=https://instance-id.enterprise.influxdb.io 
# Make sure to include a space character at the end of this command.

Log in to your instance

Log in to your instance with the OAuth device-code flow. InfluxDB 3 Cloud authenticates you with your InfluxData account, so you don’t need a token to use the CLI interactively.

Run the following command and follow the printed instructions:

influxdb3 auth login --oauth

The output is a URL and a one-time user code. Open the URL in a browser, enter the code, and approve the request. After you approve, the CLI saves your credentials to ~/.influxdb3/credentials.json and uses them automatically for later commands, so you don’t need to pass a token.

Don’t set the INFLUXDB3_AUTH_TOKEN environment variable for interactive use. If it’s set, the influxdb3 CLI uses that token instead of your logged-in session. Run influxdb3 auth login --oauth again when your session expires.

List your databases to verify that you’re authenticated:

influxdb3 show databases

A successful response confirms that your host URL and login are configured correctly.

Create a database

Use the influxdb3 create database command to create a database. You can use an existing database or create a new one specifically for this getting started tutorial. Examples in this tutorial assume a database named get-started.

Provide the following:

  • The database name
  • Optional: a database retention period as a duration value. If no retention period is specified, the default is infinite.
influxdb3 create database \
  --retention-period 
1y
 \
  
get-started

Replace the following:

  • get-started: the name of the database to create
  • 1y: the database retention period as a duration

A newly created database can take a few seconds to appear in influxdb3 show databases.

Create a token for applications

Logging in authenticates you for interactive use with the influxdb3 CLI. For applications and automated clients, create a database token scoped to only the databases and permissions it needs. Creating tokens requires admin privileges. If your user doesn’t have admin access, ask an administrator to create a token for you.

Use the influxdb3 create token command with the --permission option to create a token with read and write access to your database.

Provide the following:

  • --permission: A resource permission string in the format db:DATABASE_NAME:read,write
  • --name: A unique name for the token
influxdb3 create token \
  --permission "db:
get-started
:read,write" \
  --name "Read/write token for 
get-started
 database"

Replace get-started with the name of the database to grant the token access to.

The command returns the token string.

Store your token securely

InfluxDB displays the token string only when you create it. Store your token securely—you cannot retrieve it from the database later.

Applications can authenticate with the token by setting the INFLUXDB3_AUTH_TOKEN environment variable or passing the --token option.

Authentication in InfluxDB 3 Cloud

For interactive use, you authenticate as a user with influxdb3 auth login --oauth — no token required. For applications, create and manage tokens with the influxdb3 CLI:

  • Database tokens: Grant scoped read and/or write access to specific databases.
  • Admin tokens: Grant full administrative access. Create named admin tokens with influxdb3 create token --admin --name "NAME".

For more information, see Manage tokens.

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2