OpenSearch: 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 OpenSearch 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 OpenSearch cloud solution with a range of benefits, including:

  • Optimal performance and enhanced security on a private, dedicated VM.
  • Custom domain name support, secured by default with HTTPS encryption.
  • Integrated OpenSearch Dashboards for seamless data visualization.

Save time and make your life easier: it only takes 5 minutes to try out Stackhero's OpenSearch cloud hosting solution!

The examples below use the entry-level instance 20G for OpenSearch by default. This is a reliable choice for most workloads, but you can adjust it as needed. To see all available instance types for OpenSearch, 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
    Launch a real OpenSearch 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 OpenSearch

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