MinIO: 3. Choose the instance size

This documentation is part of the GitHub Actions & GitLab CI guide. You can view the complete guide here: Launch a real MinIO service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and automatically tear it down.

👋 Welcome to the Stackhero documentation!

Stackhero offers a ready-to-use MinIO Object Storage platform designed for reliability and speed. The main advantages include:

  • Unlimited data transfers with no hidden fees.
  • Simple, predictable, and transparent pricing.
  • A custom domain name secured with HTTPS (for example, https://object-storage.your-company.com).
  • Smooth, one-click updates with no manual intervention required.
  • High performance and security on private, dedicated infrastructure.
  • Available in both 🇪🇺 Europe and 🇺🇸 USA regions.

Simplify your workflows and save setup time: you can deploy Stackhero's MinIO Object Storage hosting in just 5 minutes.

The examples below use the entry-level instance 100G for MinIO by default. This is a reliable choice for most workloads, but you can adjust it as needed. To see all available instance types for MinIO, run:

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

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Launch a real MinIO service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and automatically tear it down
  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 MinIO

  1. Getting started
    How to begin using MinIO for S3-compatible object storage
  2. Automate with the CLI
    Start MinIO, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI