OpenSearch: 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 OpenSearch 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 provides a fully managed OpenSearch cloud environment designed for both performance and security:

  • High performance and strong security on a private, dedicated infrastructure.
  • Use your own custom domain name, protected with HTTPS by default.
  • Built-in OpenSearch Dashboards for easy data exploration and visualization.

Cut out setup and maintenance hassles: you can be up and running with OpenSearch cloud hosting from Stackhero in just a few minutes.

The examples below use the entry-level instance 20G for OpenSearch 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 OpenSearch, you can run:

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

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Spin up a real OpenSearch 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 OpenSearch

  1. Troubleshooting
    Errors you can encounter with OpenSearch
  2. Automate with the CLI
    Start OpenSearch, retrieve its credentials, and change its configuration programmatically with the Stackhero CLI