Search service
Services/OpenSearch

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.

On Wodby

How OpenSearch runs on Wodby

What Wodby sets up for this OpenSearch service. It runs the official OpenSearch image as a single node, configured through environment variables set by the manifest.

How applications reach it

  • The manifest leaves the image's security plugin with its demo configuration on. The REST API on port 9200 is therefore served over HTTPS with the image's self-signed demo certificate: use https://<app service name>:9200, and the client must skip certificate verification or trust that certificate. Plain http:// requests are refused.
  • User admin. Its password is generated by Wodby (token password) and is in OPENSEARCH_INITIAL_ADMIN_PASSWORD inside this container. The image applies it when it first installs the security configuration.
  • A service linked to this one receives host, port and the password in variables named by the linking service; read them in code and do not copy the password into the repository.
  • The image's other demo accounts have public passwords, so they are removed each time the node starts. kibanaserver remains for OpenSearch Dashboards, with a generated password (token dashboards_password). Create your own users through the security API rather than reusing these names.
  • All ports are private: no public route is created. 9300 is the transport port and 9600 the performance analyzer; applications use 9200 only.

What is configured

  • discovery.type is single-node; the service is not scalable. An index with replicas stays yellow because there is no second node: create indices with zero replicas.
  • The cluster name is built from the application and environment names.
  • bootstrap.memory_lock is false.
  • The JVM heap comes from OPENSEARCH_JAVA_OPTS (the manifest sets a fixed heap). The container memory limit must leave room above the heap.

Changing configuration

OpenSearch settings are environment variables on this service, named exactly like the setting (for example cluster.name). Do not mount an opensearch.yml. Disabling the security plugin changes the scheme to http:// and removes authentication for every linked service.

Data

Indices are in /usr/share/opensearch/data on the data volume. The manifest declares no backups, imports or actions; snapshots need a repository configured in OpenSearch itself.

Check the result

From this service's container:

  • curl -sk -u "admin:$OPENSEARCH_INITIAL_ADMIN_PASSWORD" https://localhost:9200/_cluster/health?pretty
  • curl -sk -u "admin:$OPENSEARCH_INITIAL_ADMIN_PASSWORD" https://localhost:9200/_cat/indices?v

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

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.

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