Search service

OpenSearch service

Self-hosted OpenSearch service for indexing application data, full-text search, and search analytics.

Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.

All services

Why teams use this service

Technical profile

Review versions, ports, source, and packaging.

Stacks that use it

See where this service fits in ready-made stacks.

Runtime wiring and defaults

See ports, links, storage, configs, and runtime behavior.

Overview

Technical profile and packaging

This page shows how OpenSearch is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

Search service

Versions

3.8

Source repository

wodby/service-opensearch

Public Helm chart

wodby/stateful

Ports and protocols

9200/TCP, 9300/TCP, 9600/HTTP

Labels

opensearch, search

Persistent volumes

OpenSearch data

Stacks

Use it inside ready-made stacks or your own

These public stacks already include OpenSearch as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.

OpenSearch

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Endpoints

9200/TCP, 9300/TCP, 9600/HTTP

Technical domains

HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.

Volumes

OpenSearch data