Component
core/datastore/elasticsearch
An Elasticsearch search and analytics engine. Indexes documents for full-text and analytical queries and indexes embedding vectors beside them in dense-vector fields, answering similarity searches, so a component that retrieves by similarity can be wired here. Indexes are created through Elasticsearch's own API at runtime; the component declares the server, not its contents. It runs as one node. Exports its host, port, protocol, an endpoint joining them and the account a client signs in as. Authentication stays on with the built-in superuser, elastic: its password is the attached credential, which the Kubernetes Recipe reads from its Secret by reference, and with none attached it is a development default that attaching one replaces. The server's own first-start setup, which generates certificates and prints a password, is switched off. The API is served over plain HTTP, not encrypted, and is reachable only inside the Release. Elastic publishes the image under the Elastic License 2.0. Realized on Kubernetes by a Recipe that synthesizes the server from that image, and by a Compose Recipe for local development; the host's vm.max_map_count kernel setting is the operator's to raise. Its Recipes are verified by their rendered output, not by a started server.
Provenance
- Content digest
- sha256:f5c926ccb6e34bf8c84f40038ee895adf6a16231dde9bfeb9e6624b3a53fd709
- Published
- 2026-11-10T10:10:34Z
- Signing identity
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officialapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:85339df7b303229c45648b6fd09dbb379a8aa38ace8c8078480d7da8548bf0f8
Reference at this version
oci://hub.aggrega.ai/component/core/datastore/elasticsearch:1.0.0Developer parameters
Values the developer sets in the Aggregate.
No developer parameters declared.
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 9200 | no | Port the server's REST API is published on. Most operators should omit this and let the Recipe assign the default (9200). The server listens on it on both targets; on Kubernetes it is also the Service port. It must differ from 9300 and 8080, which the server already listens on; the build halts otherwise. |
| engine_version | string | 9.5.5@sha256:13b4a40bb095774f5fda635e45fd5677cc6a26565e42b24997b0c72b88e75984 | no | Tag of the docker.elastic.co/elasticsearch/elasticsearch image every Recipe runs, optionally followed by @ and the digest it must resolve to. The Recipes configure the server through the settings of the 9.x releases; another release may need other ones. |
| compute | object | — | no | — |
| storage | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Output contract
Values this component publishes to consumers over the uses topology.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| host | string | — | yes | Address a client connects to. On Kubernetes it is the Service's DNS name, and on Compose the service name. |
| port | integer | — | yes | TCP port the server's REST API answers on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming 9200. |
| user | string | — | no | Name of the account a client signs in as — `elastic`, the server's built-in superuser. The matching password arrives through the credential attached to the component, never through this contract. |
| protocol | string | — | no | Scheme a client composes the server's address with — `http`, as in http://<host>:<port>; the REST API is served over HTTP. |
| endpoint | string | — | no | The server's address as one URI, http://<host>:<port>, for a client that takes one address rather than its parts. It carries no credential. |
Uses sockets
The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.
No uses sockets declared.
Attachment slots
Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.
| Slot | Selector | Required | Inject | Sensitive | Description |
|---|---|---|---|---|---|
| password | feature.aggrega.ai/kind=secret | no | env | yes | Optional password of the server's built-in superuser, elastic. When attached, the Kubernetes Recipe reads it from the credential's Secret by reference and the Compose Recipe writes the value the credential delivers; unattached, compose/elasticsearch and helm/elasticsearch set it to the development literal `apppass`, which this catalog publishes, so every Release that leaves the slot unattached shares that password, and attaching a credential replaces it. |
Self-inject allowlist
env
Relationships
Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.
Uses
This entity uses nothing in the catalog.
Used by
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «knowledge_base»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «state_store»
uses socket «vector_store»
uses socket «vector_store»
uses socket «task_memory»
uses socket «document_store»
uses socket «vector_store»
uses socket «vector_store»
uses socket «checkpointer_db»
uses socket «checkpointer_db»
uses socket «backend»
uses socket «backend»
uses socket «backend»
uses socket «vector_store»
uses socket «vector_store»
uses socket «storage»
uses socket «knowledge_base»
uses socket «data_store»
uses socket «metadata_store»
uses socket «target_datastore»
uses socket «target_datastore»
uses socket «target_datastore»
uses socket «backend»
uses socket «databases»
uses socket «etcd»
uses socket «backend»
uses socket «backend»
uses socket «cache»
uses socket «state_store»
uses socket «forward_target»
uses socket «backend»
uses socket «cache»
uses socket «chunk_cache»
uses socket «scrape_target»
uses socket «backend»
uses socket «backend»
uses socket «database»
applies to
applies to
applies to
implements
implements