ClusterNest now runs an MCP server, so a coding agent can create clusters, rotate credentials, manage organizations and read invoices directly. Paste one URL into your client, log in through the browser, and it works inside your own account.
Read itclusternest.com has been rebuilt, and the blog now runs on it rather than on the documentation site. Every post kept its slug, and the old addresses redirect: posts, tag pages and both feeds.
Read itOpenSearch 3.8 is live on ClusterNest, with faster vector search, a broader set of AI agent integrations, and new tools for exploring logs without leaving Dashboards.
Read itWe've shipped two updates that make it easier to automate ClusterNest end-to-end: a simpler way to authenticate against the API programmatically, and a Terraform provider release that's faster on long applies and can now manage organizations directly.
Read itOpenSearch 3.7 just landed on ClusterNest, with a strong focus on observability and query safety.
Read itBig milestone: OpenSearch 3.6 is live on ClusterNest, and it's the project's first Long-Term Support release, with 18+ months of guaranteed support, so it's a solid pick for clusters you don't want to babysit through every minor upgrade.
Read itOpenSearch 3.3 and 3.4 are selectable on ClusterNest clusters. In the same change, OpenSearch 2.x is deprecated here: still running, no longer offered on new clusters.
Read itMetrics on the same terms as logs. Managed Prometheus is open in beta: a remote write endpoint and PromQL over a cluster you size by tier and node count, priced the same way as our OpenSearch service.
Read itOpenSearch 3.2 can be selected on new and existing clusters. The console handles it, and Terraform provider 1.1.2 adds it to the version list.
Read itThe ClusterNest Console has been rebuilt from the ground up. Dark mode throughout, one visual language from the landing page to the cluster list, and the settings that used to be Terraform-only are now in the interface.
Read itOpenSearch clusters can now snapshot to an S3 bucket you control, on AWS or any S3-compatible store. Authentication is an IAM role or static keys, and the copy is yours whatever happens to your account with us.
Read itOpenSearch 3.0 and 3.1 can now be selected on ClusterNest clusters. It is the first major release since 2.0, rebased on Lucene 10 and requiring Java 21, so it is a version worth reading the notes for before you move.
Read itAdvanced tier OpenSearch clusters are open to everyone. Eight vCPU, 64 GiB and 2 TB of NVMe per node, launched from the console with no quota request and no waiting for an approval.
Read itOpenSearch clusters can now delegate authentication to your identity provider over SAML or OIDC, so access follows the directory you already run. It costs nothing extra, on every tier.
Read itClusters can now be declared in Terraform rather than clicked into existence. The ClusterNest provider is out of preview: create, update and destroy OpenSearch clusters from the same repository as the rest of your infrastructure.
Read itv2 of the ClusterNest API publishes a full OpenAPI schema, so you can generate a client rather than write one. It also brings its own authentication: two-factor, passkeys and app passwords. The console already runs on it.
Read itTwo years after launching managed OpenSearch, we are closing the Elasticsearch service to new clusters. Existing customers keep running, and we will come to you about the migration rather than the other way round.
Read itThe service we said we were building in July is open. Managed OpenSearch clusters, priced by tier and node count like our Elasticsearch service, with OpenSearch Dashboards included and a migration we run with you.
Read itOpenSearch has reached a stable release. We said in January that the answer to the Elasticsearch relicensing was an engine that is genuinely open with more than one vendor behind it, and this is the one. A managed service is in build.
Read it