InfluxDB: 3. Pick the instance size

This documentation is part of the GitHub Actions & GitLab CI guide. View the full guide here: Spin up a real InfluxDB service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and tear it down automatically.

👋 Welcome to the Stackhero documentation

Stackhero delivers a fully managed InfluxDB cloud environment, designed for speed and simplicity:

  • Unlimited writes, queries, dashboards, tasks, and buckets.
  • Unlimited data retention: keep your metrics as long as you need.
  • Unlimited network and disk transfers, with no hidden limits.
  • One-click updates: always access the latest features and fixes.
  • Consistent performance and strong security on your own private, dedicated infrastructure.

With Stackhero, you can focus on your data and insights. Getting started with InfluxDB cloud hosting only takes a few minutes, and every setup is optimized for long-term reliability.

The examples below use the entry-level instance 10G for InfluxDB by default. This is a solid choice for most workloads, but you are welcome to adjust it as needed. To view all available instance types for InfluxDB, you can run:

# The NAME column shows the value to pass to --instance
stackhero instances-store-list --service-store=influxdb

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Spin up a real InfluxDB service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and tear it down automatically
  2. 1. Create an access token and store it as a CI secret
  3. 2. The lifecycle script
  4. 4. GitHub Actions
  5. 5. GitLab CI

Other articles for InfluxDB

  1. Introduction
    Introduction to InfluxDB, everything you need to know about it
  2. Getting started
    How to get started with InfluxDB
  3. Automate with the CLI
    Start InfluxDB, retrieve its credentials, and change its configuration programmatically with the Stackhero CLI