Appearance

OpenSearch ​

OpenSearch is an open-source search and analytics suite. Enabling this service gives your project one or more dedicated OpenSearch instances to power full-text search, log analytics, and more for your application.

Enabling OpenSearch ​

OpenSearch is an add-on service and is not enabled by default. For now, our support team sets up each OpenSearch instance for your project. Self-service provisioning is on our roadmap, but isn't available yet.

INFO

To use OpenSearch for your project, please contact our support team with your project ID and a brief description of your use case. Our team will set up a dedicated OpenSearch instance for your project and configure the connection details. If you need more than one instance (for example, one per environment), just ask.

Viewing your configuration ​

Once OpenSearch has been set up for your project, you can view every instance under Services > OpenSearch. For each instance, you'll find:

  • The host and port of that OpenSearch instance
  • Whether TLS is enabled, i.e. whether to connect via https or http
  • The username and password to authenticate with

Together, these make up your application's connection URL, for example https://<username>:<password>@<host>:<port>.

WARNING

Depending on the instance, these credentials may belong to an admin user or to a user restricted to your project. Only use them server-side, never in frontend code, and keep them in your own secrets management.

Creating a more restricted user ​

If your application needs narrower access than the provided credentials grant, for example read-only access to specific indices, you can create a dedicated user and role through OpenSearch's security plugin, provided your credentials are allowed to manage users. See OpenSearch's guide to defining users and roles and its security REST API reference, then configure your application with that user instead.

Hubble Studio does not create, list, or delete any of these users for you.

WARNING

Because additional users and roles are created and deleted directly against each OpenSearch instance, Hubble Studio has no way of knowing which ones currently exist. Keep track of them yourself, for example in your own secrets management.