No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon OpenSearch Service vs Elastic Observability comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Feb 22, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Amazon OpenSearch Service
Ranking in Application Performance Monitoring (APM) and Observability
22nd
Ranking in Log Management
18th
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
13
Ranking in other categories
Search as a Service (3rd)
Elastic Observability
Ranking in Application Performance Monitoring (APM) and Observability
11th
Ranking in Log Management
15th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
29
Ranking in other categories
IT Infrastructure Monitoring (15th), Container Monitoring (5th), Cloud Monitoring Software (11th)
 

Mindshare comparison

As of May 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Amazon OpenSearch Service is 1.1%, down from 1.9% compared to the previous year. The mindshare of Elastic Observability is 1.9%, down from 5.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Mindshare Distribution
ProductMindshare (%)
Elastic Observability1.9%
Amazon OpenSearch Service1.1%
Other97.0%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Md. Shahariar Hossen - PeerSpot reviewer
Senior Software Engineer at Cefalo
Event tracking has become smoother and data analytics provide clear insights for user actions
Amazon OpenSearch Service is not providing the processing feature directly. From Amazon OpenSearch Service, we are actually maintaining the AWS SQS, the queue service, which is responsible for providing information about what data has to be modified. So using that SQS, we're actually providing it, but we're not directly using Amazon OpenSearch Service for keeping data to other data pipeline thing. So far we didn't use it for any machine learning purposes, but in future, we have plans to extend or implement this feature. Since AWS itself is secure and Amazon OpenSearch Service is a part of this entire ecosystem, it becomes much easier for security purposes. From the validation point of view, Amazon OpenSearch Service itself provides easy to communicate APIs and up-to-date documents, which is much beneficial. For example, if I'm missing anything, I can directly go and check the documentation. That is actually much easier. I would rate it as really good so far. It's much faster. For our local machine, we can also use a kind of replica of Amazon OpenSearch Service just for development purposes. That is another good feature. I would say for the encryption thing and also the user access control management, it's much faster. For some of these hashing algorithms, it also worked really well so far. To be honest, I didn't find any places where it can be improved. However, I think they could provide more abstraction. For example, still for searching, we have to write down the queries in a specific manner, such as for a specific JSON structure or in a specific way. Otherwise, they don't provide us the actual results. For at least this purpose, I think abstraction could be a bit easier or a bit improved. Other than that, right now there is the age of AI, so some kind of prompting could also work, but I'm not sure how it could be integrated. As a user, lower prices or reasonable pricing is always better. Those can be improved as well. However, it is good that most of the services including Amazon OpenSearch Service actually provide pay as you go pricing. So if there were a bit lower version or a bit less payment methodology, it might be much better.
Mohammed-Abdelalim - PeerSpot reviewer
Assistant Vice President at QualityKiosk Technologies Pvt. Ltd.
Has provided powerful customization for unique monitoring needs but needs more out-of-the-box capabilities
In my opinion, the best features of Elastic Observability are their flexibility to integrate with other existing systems and the ability to build a unified monitoring tool that can integrate with existing ones and end-to-end user journeys which require a lot of customizations. The greatest feature in Elastic is the ability to customize. This is similar to my comments about customizable dashboards in Elastic because it's visible to the analyst. However, it's very great. Customizing these dashboards can meet the customer's specific use cases and specific stories that they have in their environment, their special environment that doesn't look like other environments. The dashboarding in Elastic is highly customizable to the level of logos. If the customer wants his company logo in the dashboard, it can be done.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Regarding valuable features of the solution, we found with the process, which we have used in both cases where we used the solution that while you're seeing the streaming of data, you can analyze in the initial phase what sort of data you are streaming and whether it is valuable."
"Amazon OpenSearch Service provides a managed database solution, so we don't need to manage everything ourselves."
"Amazon OpenSearch Service has enhanced our organization's ability to store and search large amounts of data efficiently."
"The business analytics capabilities are the most important feature it provides."
"They have the good documentation in the help text and that is the reason the Amazon is the perfect solution in the current market."
"The stability of the product is good."
"The most valuable features of Amazon Elasticsearch are ease of use, native JSON, and efficiency. Additionally, handles many use cases and search grammar was useful."
"In case there is a failure, Elastic manages everything well, and there no major downtime."
"The tool's most valuable feature is centralized logging. Elastic Common Search helps us to search for the logs across the organization."
"Elastic provides built-in features for queries and report generation. It's a very good tool for monitoring integration capabilities."
"All the features that we use, such as monitoring, dashboarding, reporting, the possibility of alerting, and the way we index the data, are important."
"I found Elk to be excellent for log analytics, security analytics, application code-level analytics, collaboration with DevOps teams, CI/CD, microservices, and Kubernetes, specifically cloud-native or cloud-specific tasks."
"The architecture and system's stability are simple."
"Elastic Observability significantly improves incident response time by providing quick access to logs and data across various sources. For instance, searching for specific keywords in logs spanning over a month from multiple data sources can be completed within seconds."
"Machine learning is the most valuable feature of this solution."
"Good design and easy to use once implemented."
 

Cons

"The pricing aspect is a concern. The service is way too costly. For the past month, I used only 30 to 40 MB of data, and the cost was $500. AWS could improve pricing."
"As a user, lower prices or reasonable pricing is always better."
"There is the problem with the database. Amazon only provides the host to run to our applications bias, but there is no option to manage the database within the Elasticsearch product."
"I would say that, basically, the configuration part is an area with a shortcoming...Some upgradation is required on the configuration side so that we can get to use it."
"They can enhance data visualization."
"In terms of data handling capabilities with Amazon OpenSearch Service, they can be complex and managing data in comparison to other SIM solutions is a major drawback, as it is very hard to handle the data."
"Amazon Elasticsearch can improve the bullion in the near search and the ease of integration with Kibana. Additionally, there could be more flexibility in the configuration and documentation."
"There is a problem with the database. Amazon only provides the hosting to run our applications bias, but there is no option to manage the database within the Elasticsearch product."
"Elastic Observability’s price could be improved."
"I would advise others to use a different solution than Elastic APM."
"Elastic Observability is reactive rather than proactive. It should act as an ITSM tool and be able to create tickets and alerts on Jira."
"With Elastic, you need to code and program more things compared to Dynatrace."
"They need more skills in the market. There are not enough skills in the market. It is not pervasive enough on the market, in my opinion. In other words, there isn't a big enough user base."
"The solution would be better if it was capable of more automation, especially in a monitoring capacity or for the response to abnormalities."
"There is room for improvement regarding its APM capabilities."
"It lacked some capabilities when handling on-prem devices, like network observability, package flow analysis, and device performance data on the infrastructure side."
 

Pricing and Cost Advice

"The solution is not expensive, but priced averagely, I will say."
"You only pay for what you use."
"There is a community edition available and the price of the commercial offering is reasonable."
"Compared to other cloud platforms, it is manageable and not very expensive."
"There are two types: cloud and SaaS. They charge based on data ingestion, ingest rate, hard retention, and warm retention. I believe it costs around $25,000 annually to ingest 30GB of data daily. That is the SaaS version. There is also a self-managed license where the customer manages their own infrastructure on-prem. In such cases, there are three license tiers that respectively cost $5,000 annually per node, $7,000 per node, and $12,500 per node."
"Elastic Observability's pricing could be better for small-scale users."
"The product’s pricing needs improvement."
"Pricing is one of those situations where the more you use it, the more you pay."
"Users have to pay for some features, like the alerts on different channels, because they are unavailable in different source versions."
"We have been using the open-source version."
"One needs to pay for the licenses, and it is an annual subscription model right now."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
893,244 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
10%
Computer Software Company
10%
Government
6%
Financial Services Firm
15%
Computer Software Company
12%
Government
7%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise2
Large Enterprise3
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise16
 

Questions from the Community

What do you like most about Amazon OpenSearch Service?
We retrieve historical data with just a click of a button to move it from cold to hot or warm because it's already stored in the backend storage
What is your experience regarding pricing and costs for Amazon OpenSearch Service?
I would consider the pricing as a six based on how much data we are handling; if we handle minimal data, it's cheap, but for large data, it becomes costly. Our clients usually pay between $1,000 to...
What needs improvement with Amazon OpenSearch Service?
Amazon OpenSearch Service is not providing the processing feature directly. From Amazon OpenSearch Service, we are actually maintaining the AWS SQS, the queue service, which is responsible for prov...
What is your experience regarding pricing and costs for Elastic Observability?
The problem is their licensing model, which is a bit confusing. Many customers struggle to understand their total cost of ownership because Elastic licensing is not dependent on easy, quantifiable ...
What needs improvement with Elastic Observability?
After careful consideration about areas for improvement in Elastic Observability, aspects such as pricing, customization, implementation, and scalability could be improved. As a user of the system,...
What is your primary use case for Elastic Observability?
My use case for Elastic Observability is observability, as we upload our customers' data, including logs, and when there is an issue, we can analyze what went wrong.
 

Also Known As

Amazon Elasticsearch Service
No data available
 

Overview

 

Sample Customers

VIDCOIN, Wyng, Yellow New Zealand, zipMoney, Cimri, Siemens, Unbabel
PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
Find out what your peers are saying about Amazon OpenSearch Service vs. Elastic Observability and other solutions. Updated: May 2026.
893,244 professionals have used our research since 2012.