Service type
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
How applications reach it
- The manifest leaves the image's security plugin with its demo configuration on. The REST API on port
9200is therefore served over HTTPS with the image's self-signed demo certificate: usehttps://<app service name>:9200, and the client must skip certificate verification or trust that certificate. Plainhttp://requests are refused. - User
admin. Its password is generated by Wodby (tokenpassword) and is inOPENSEARCH_INITIAL_ADMIN_PASSWORDinside 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.
kibanaserverremains for OpenSearch Dashboards, with a generated password (tokendashboards_password). Create your own users through the security API rather than reusing these names. - All ports are private: no public route is created.
9300is the transport port and9600the performance analyzer; applications use9200only.
What is configured
discovery.typeissingle-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_lockisfalse.- 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?prettycurl -sk -u "admin:$OPENSEARCH_INITIAL_ADMIN_PASSWORD" https://localhost:9200/_cat/indices?v
Overview
Technical profile and packaging
Versions
Source repository
Public Helm chart
Ports and protocols
Labels
Persistent volumes
Stacks
Use it inside ready-made stacks or your own
Runtime wiring
Reuse connectivity, storage, and runtime defaults
Endpoints
Technical domains
Volumes