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

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

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

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

  1. Getting Started
    Everything you need to know about Elasticsearch
  2. Automate with the CLI
    Start Elasticsearch, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI
  3. Ingest Attachment Plugin
    How to extract data from PPT, XLS, and PDF files to Elasticsearch