Documentation

Cancel your InfluxDB Cloud Serverless subscription

To cancel your InfluxDB Cloud Serverless subscription, complete the following steps:

  1. Stop reading and writing data.
  2. Export data and other artifacts.
  3. Cancel service.

Stop reading and writing data

To stop being charged for InfluxDB Cloud Serverless, pause all writes and queries.

Export data and other artifacts

Save Telegraf configurations

  1. Click the Load Data icon in the navigation bar.

  2. Select the Telegraf tab. A list of existing Telegraf configurations appears.

  3. Click the name of a Telegraf configuration.

  4. Click Download Config to save.

Export data

To export all your data, query your data out in time-based batches and store it in to an external system or an InfluxDB OSS instance.

Cancel service

  1. Click the account name in the header of your InfluxDB Cloud Serverless user interface (UI) and select Billing.

  2. Do one of the following:

  • If you subscribed to an InfluxDB Cloud Usage-Based Plan through AWS Marketplace, click the AWS link, click Unsubscribe, and then click Yes, cancel subscription.
  • If you subscribed to an InfluxDB Cloud Usage-Based Plan through GCP Marketplace, click the GCP link, click Unsubscribe, and then click Yes, cancel subscription.
  • If you subscribed to an InfluxDB Cloud Usage-Based Plan through InfluxData, click Cancel Service. Select I understand and agree to these conditions, and then click I understand, Cancel Service. Click Confirm and Cancel Service. Your payment method is charged your final balance immediately upon cancellation of service.

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 Serverless