OpenSearch

OpenSearch SSO overview A ClusterNest managed OpenSearch cluster can authenticate users against external identity providers. You configure them as a list of auth_sources. Each source is either OIDC or SAML, and each has a unique name.

Configure Logging with ClusterNest Managed OpenSearch Set up centralized logging with Fluent Bit and ClusterNest Managed OpenSearch: provision a cluster via the Console or Terraform, forward logs with Fluent Bit, and visualize them in OpenSearch Dashboards.

Connect an AI agent to your OpenSearch cluster OpenSearch ships its own MCP server inside the ML Commons plugin. Turning it on lets an agent search your indices, read mappings and run PPL against the data in the cluster, rather than being handed a query language and left to construct HTTP calls itself.

How to configure OpenSearch S3 snapshots with ClusterNest OpenSearch supports backing up and restoring data to AWS S3 or an S3-compatible storage by configuring a snapshot repository.

Ship Kubernetes Logs to ClusterNest Managed OpenSearch Without Static Credentials This guide collects container logs from one or more Kubernetes clusters into a ClusterNest Managed OpenSearch cluster, with no password, API key or other static credential anywhere in the pipeline. Each log shipper signs in with the identity Kubernetes already gives its pod, so there is nothing to store in a Secret, share between clusters or rotate. Each cluster can write only its own logs, and people read them by signing in through your identity provider.