Elastic, the company behind Elasticsearch and the Elastic Stack, announced the next evolution in the Elasticsearch Service on Elastic Cloud to solve more use cases, operate at a larger scale, and give customers even more capabilities to customize their deployments.
Now known simply as the Elastic Elasticsearch Service, this is the only service offered and supported by Elastic.
New features include optimized deployment templates for the most common use cases, more hardware choices, support for hot-warm architectures, machine learning, and a revised pricing model, including a new free tier to help new customers get started.
"Elastic customers are putting more and more data into the Elasticsearch Service for their mission-critical use cases, and we've responded by making it more efficient, more customizable, more cost effective and more powerful," said Shay Banon, Elastic founder and CEO. "Elastic's engineering mission has always been to make complex things simple. The latest version of the Elasticsearch Service is doing that and more, making it easier for companies to gain immediate insights from large volumes of data across some of the most challenging search and analytics, logging, or security scenarios."
The key new features of the Elasticsearch Service include:
- Optimized Deployments Based on Use Case. From logging to security analytics to application search, companies are using Elasticsearch to solve some of the largest search problems. Customers now have the option to select out-of-the-box deployment templates to optimize the underlying hardware for their use cases based on the expected workload - I/O, CPU, or memory intensive.
- Hot-Warm Deployments with Index Lifecycle Management. One of the most powerful features of the new Elasticsearch Service is the hot-warm architecture template, which enables organizations to ingest and query current data quickly, while keeping older, longer-term data on denser and more cost-effective hardware. Customers can now quickly deploy this architecture in minutes and automate index lifecycle management without having to modify any configuration files.
- Dedicated Master Nodes. Organizations use the Elasticsearch Service to solve problems at petabyte scale and need their Elasticsearch clusters to scale with them. The Elasticsearch Service now provides the ability to deploy dedicated master nodes to better support larger deployments.
- New User Console that Simplifies Customization. The Elasticsearch Service has a new UI to make it easy for customers to define and configure all of the Elastic Stack components supported by the Elasticsearch Service from one page. For example, new sliders enable customers to scale Kibana instances or add more RAM to their master nodes with ease.
- Machine Learning for All Deployments. Thousands of Elastic customers already use Elastic's machine learning features to detect anomalous behavior, and reduce time to root cause analysis. Customers can now quickly add machine learning features to each of their Elasticsearch Service deployments and start gaining insights immediately.
- New Reduced Pricing. Elastic has made the Elasticsearch Service more accessible with a new lower starting price and a free tier. Pricing now follows a simple linear model based on size and number of availability zones. Additionally, each deployment can now include multiple types of nodes and instances, such as Elasticsearch data nodes, Elasticsearch master nodes, and Kibana instances, with each instance priced separately. For more information on the new pricing and the free tier, along with frequently asked questions, please visit Elastic's pricing blog.
- Elastic Rebrands its Software-as-a-Service (SaaS) Solutions. In addition to the new Elasticsearch Service naming, Elastic also announced the rebranding of the Swiftype hosted solutions to Elastic Site Search Service and Elastic App Search Service. Elastic Cloud is a collection of all Elasticsearch-powered SaaS solutions from Elastic.
The Latest
I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...