Try our new research platform with insights from 80,000+ expert users

Amazon OpenSearch Service vs Elastic Search comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 16, 2025

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 Search as a Service
3rd
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
13
Ranking in other categories
Application Performance Monitoring (APM) and Observability (23rd), Log Management (19th)
Elastic Search
Ranking in Search as a Service
1st
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
88
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Vector Databases (2nd)
 

Mindshare comparison

As of February 2026, in the Search as a Service category, the mindshare of Amazon OpenSearch Service is 9.6%, down from 10.2% compared to the previous year. The mindshare of Elastic Search is 18.3%, up from 14.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Market Share Distribution
ProductMarket Share (%)
Elastic Search18.3%
Amazon OpenSearch Service9.6%
Other72.1%
Search as a Service
 

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.
Vaibhav Shukla - PeerSpot reviewer
Senior Software Engineer at Agoda
Search performance has transformed large-scale intent discovery and hybrid query handling
While Elastic Search is a good product, I see areas for improvement, particularly regarding the misconception that any amount of data can simply be dumped into Elastic Search. When creating an index, careful consideration of data massaging is essential. Elastic Search stores mappings for various data types, which must remain below a certain threshold to maintain functionality. Users need to throttle the number of fields for searching to avoid overloading the system and ensure that the design of the document is efficient for the Elastic Search index. Additionally, I suggest utilizing ILM periodically throughout the year to manage data shuffling between clusters, preventing hotspots in the distribution of requests across nodes.

Quotes from Members

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

Pros

"The stability of the product is good."
"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"
"In case there is a failure, Elastic manages everything well, and there no major downtime."
"The customer service is excellent, rated nine out of ten."
"Our customers have seen tangible benefits from Amazon OpenSearch Service, especially in terms of their applications running smoothly, so they do get a return on investment."
"They have the good documentation in the help text and that is the reason the Amazon is the perfect solution in the current market."
"It enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs."
"Amazon OpenSearch Service has enhanced our organization's ability to store and search large amounts of data efficiently."
"From the customer side, Elastic Search is super fast and very efficient, delivering results quickly."
"The special text processing features in this solution are very important for me."
"The most valuable feature of the solution is its utility and usefulness."
"We had many reasons to implement Elasticsearch for search term solutions. Elasticsearch products provide enterprise landscape support for different areas of the company."
"It gives us the possibility to store and query this data and also do this efficiently and securely and without delays."
"I really like the visualization that you can do within it. That's really handy. Product-wise, it is a very good and stable product."
"Data indexing of historical data is the most beneficial feature of the product."
"The most valuable feature is the out of the box Kibana."
 

Cons

"We faced documentation challenges during integration after migrating from Elasticsearch to Amazon OpenSearch Service. Better documentation on integration, query handling, and a more user-friendly UI could enhance the product."
"As a user, lower prices or reasonable pricing is always better."
"They can enhance data visualization."
"The configuration should be more straightforward because we had to select a lot of things."
"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"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."
"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."
"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."
"There are some features lacking in ELK Elasticsearch."
"There are challenges with performance management and scalability."
"I would rate technical support from Elastic Search as three out of ten. The main issue is a general sum of all factors."
"Better dashboards or a better configuration system would be very good."
"I think the biggest issue we had with Elastic Search was regarding integrations with our multi-factor authentication tool."
"There is an index issue in which the data starts to crash as it increases."
"Elastic Search needs to improve authentication. It also needs to work on the Kibana visualization dashboard."
"They should improve its documentation. Their official documentation is not very informative. They can also improve their technical support. They don't help you much with the customized stuff. They also need to add more visuals. Currently, they have line charts, bar charts, and things like that, and they can add more types of visuals. They should also improve the alerts. They are not very simple to use and are a bit complex. They could add more options to the alerting system."
 

Pricing and Cost Advice

"There is a community edition available and the price of the commercial offering is reasonable."
"The solution is not expensive, but priced averagely, I will say."
"You only pay for what you use."
"Compared to other cloud platforms, it is manageable and not very expensive."
"The price of Elasticsearch is fair. It is a more expensive solution, like QRadar. The price for Elasticsearch is not much more than other solutions we have."
"There is a free version, and there is also a hosted version for which you have to pay. We're currently using the free version. If things go well, we might go for the paid version."
"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"we are using a licensed version of the product."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"We are using the free open-sourced version of this solution."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
881,665 professionals have used our research since 2012.
 

Top Industries

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

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 Business37
Midsize Enterprise10
Large Enterprise43
 

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 do you like most about ELK Elasticsearch?
Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
Elastic Search's pricing totally depends on the server. Managed services from AWS are used, and we have worked on a self-managed Elastic Search cluster. On the AWS side, it is very expensive becaus...
What needs improvement with ELK Elasticsearch?
To be honest, there is only one downside of Elastic Search that makes sense because we use a basic license, which is a free license. We do not have some features available because of the free licen...
 

Also Known As

Amazon Elasticsearch Service
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

VIDCOIN, Wyng, Yellow New Zealand, zipMoney, Cimri, Siemens, Unbabel
T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Find out what your peers are saying about Amazon OpenSearch Service vs. Elastic Search and other solutions. Updated: December 2025.
881,665 professionals have used our research since 2012.