Skip to content
← All services

Search

Managed OpenSearch on your own cluster

Full-text search and analytics over your data: the Apache-licensed fork of Elasticsearch.

Created inside a project, beside the apps that use it. Each project gets its own instance, storage and credentials.

01What it does

OpenSearch, run for you

OpenSearch on the OpenSearch project's own chart, as a single node.

Indexes documents, ranks results and answers aggregation queries, with the API the Elasticsearch clients speak. Half of the memory becomes the JVM heap and the rest caches the index, so both halves matter when you pick a size.

Bound apps get the host, port, username and password under an OPENSEARCH_ prefix. The HTTP API can be published on a hostname of its own.

02Options

What you choose

What the console asks when you create it, in the catalog's own numbers. Anything marked chosen once cannot change without creating a new instance.

Sizes
small 1Gi, medium 2Gi, large 4Gi of memory
Storage
10Gi by default, chosen once
Hostname
The HTTP API (9200) can be published on a domain
Pause
No; pause the project instead

03Binding

What your app receives

Bind it to an app and these arrive as environment variables. The values are generated once into a secret and reach the app from there, rather than as something you copy.

  • OPENSEARCH_HOST
  • OPENSEARCH_PORT
  • OPENSEARCH_USERNAME
  • OPENSEARCH_PASSWORD
  • OPENSEARCH_URL

04Adding it

Add OpenSearch to a project

The same four steps as every service in the catalog.

  1. 01Open a project and go to Services.
  2. 02Pick it from the catalog and choose its options. Only the size is required; everything else has a default.
  3. 03Create it. Anyport installs it into the project's namespace, generates its credentials into a secret there, and tracks its health.
  4. 04Bind it to an app. The connection details arrive as environment variables, and rotating the credential never means editing an app.
Open the console →How services work →

Also under Search