Documentation

Set up prerequisites

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.

InfluxDB Clustered requires the following prerequisites:

  • Kubernetes cluster: version 1.25 or higher
  • Object storage: AWS S3 or S3-compatible storage used to store the InfluxDB parquet files
  • PostgreSQL-compatible database (AWS Aurora, hosted Postgres, etc.): Used to store the InfluxDB catalog
    • Supported PostgreSQL versions: 13.8–14.6
  • OAuth 2.0 provider:
  • TLS certificate: for ingress to the cluster

Set up a Kubernetes cluster

  1. Deploy a Kubernetes cluster. You must Kubernetes v1.25 or higher.
  2. Create two namespaces–influxdb and kubit.
  3. Install an Ingress controller in the cluster and a mechanism to obtain a valid TLS certificate (for example: cert-manager or provide the certificate PEM manually out of band). InfluxDB Clustered currently supports Ingress NGINX, but others may work.
  4. Ensure your Kubernetes cluster can access to the InfluxDB container registry, or, if running in an air-gapped environment, a local container registry to which you will need to copy the InfluxDB images.

It is strongly recommended that you run the PostgreSQL-compatible database (that stores the InfluxDB Catalog) and the Object Store (that stores InfluxDB parquet files) in a separate namespace from InfluxDB or external to Kubernetes entirely.

Running the Catalog database and Object Store in a separate namespace or outside of Kubernetes makes management of the InfluxDB instance easier and helps to prevents accidental data loss.

Cluster sizing recommendation

For a medium-size workload, InfluxData has tested the InfluxDB Clustered using the following AWS products and sizing:

  • S3 for object store (size is determined by how much data you write)
  • Aurora Postgresql - serverless v2 scaling configuration (2-64 ACUs)
  • EC2 instances - primarily m6i.2xlarge (8 CPU, 32GB RAM)
    • 3 m6i.2xlarge instances for ingesters and routers (with minimum of 2Gi of local storage)
    • 3 m6i.2xlarge instances for queriers
    • 1 m6i.2xlarge instance for compactors
    • 1 t3.large for the Kubernetes control plane

Your sizing may need to be different based on your environment and workload, but this is a reasonable starting size for your initial testing.

Set up local storage

The InfluxDB ingester pods need local storage to store the Write-Ahead Log (WAL). The recommended minimum size of the local storage is 2 gibibytes (2Gi).

Set up an OAuth2 provider

InfluxDB requires access to an OAuth2 authentication service to authenticate user access. InfluxDB Clustered requires that the OAuth2 service supports Device Authorization Flow. InfluxData has tested with Microsoft Entra ID (formerly Azure Active Directory), Keycloak, and Auth0, but the any OAuth2 provider should work. To access the OAuth2 server, InfluxDB requires the following OAuth2 connection credentials:

  • Client ID
  • JWKS endpoint
  • Device authorization endpoint
  • Token endpoint.

Set up client Software

On the system used to configure the cluster (not the cluster itself), install the following:

Configure object storage permissions

Ensure the identity you’re using to connect to your S3-compatible object store has the correct permissions to allow InfluxDB to perform all the actions it needs to.

View example AWS S3 access policy

View the requirements for Google Cloud Storage

View the requirements for Azure Blob Storage


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: