Elasticsearch: 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 Elasticsearch 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 Elasticsearch cloud service designed for professionals who need reliable search, analytics, and logging at scale.

  • Consistent performance and strong security with a private, dedicated infrastructure.
  • Easily set up a custom domain name secured by HTTPS.

Get started quickly and focus on your work: you can have a production-ready Elasticsearch cloud hosting environment in about 5 minutes, with routine maintenance and security handled for you.

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

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

Continue reading this guide

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

  1. Getting started
    All you need to know about Elasticsearch
  2. Automate with the CLI
    Start Elasticsearch, retrieve its credentials, and change its configuration programmatically with the Stackhero CLI
  3. Ingest attachment plugin
    How to extract data from PPT, XLS, and PDF files to Elasticsearch