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

"I would definitely recommend Amazon OpenSearch Service to other professionals due to its fast and reliable search capabilities."
"In case there is a failure, Elastic manages everything well, and there no major downtime."
"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"
"The initial set up is very easy...We really appreciate Amazon!"
"It enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs."
"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 most valuable features of Amazon Elasticsearch are ease of use, native JSON, and efficiency. Additionally, handles many use cases and search grammar was useful."
"I have found the sort capability of Elastic very useful for allowing us to find the information we need very quickly."
"The best feature of Elastic Search is it does exactly what it says."
"Using real-time search functionality to support operational decisions has been helpful."
"It is a stable and good platform."
"It provides deep visibility into your cloud and distributed applications, from microservices to serverless architectures. It quickly identifies and resolves the root causes of issues, like gaining visibility into all the cloud-based and on-prem applications."
"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 analytics with Elastic benefits us due to the huge traffic volume in our organization, which reaches up to 60,000 requests per second. With logs of approximately 25 GB per day, manually analyzing traffic behavior, payloads, headers, user agents, and other details is impractical."
"The full text search capabilities in Elastic Search have proven to be extremely valuable for our operations."
"You have dashboards, it is visual, there are maps, you can create canvases. It's more visual than anything that I've ever used."
 

Cons

"One glaring issue was with our mapping configuration as the system accepted the data we posted, but after a few months, when we attempted complex queries, we realized the date formatting had become problematic."
"It would be beneficial to have some level of customization available in the managed service, tailored to the specific use cases of the end users."
"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."
"The configuration should be more straightforward because we had to select a lot of things."
"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."
"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."
"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"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."
"The GUI is the part of the program which has the most room for improvement."
"Improving machine learning capabilities would be beneficial."
"I think the biggest issue we had with Elastic Search was regarding integrations with our multi-factor authentication tool."
"There are a lot of manual steps on the operating system. It could be simplified in the user interface."
"Ratio aggregation is not supported in this solution."
"There are potential improvements based on our client feedback, like unifying the licensing cost structure."
"The real-time search functionality is not operational due to its impact on system resources."
"The solution has quite a steep learning curve. The usability and general user-friendliness could be improved. However, that is kind of typical with products that have a lot of flexibility, or a lot of capabilities. Sometimes having more choices makes things more complex. It makes it difficult to configure it, though. It's kind of a bitter pill that you have to swallow in the beginning and you really have to get through it."
 

Pricing and Cost Advice

"The solution is not expensive, but priced averagely, I will say."
"Compared to other cloud platforms, it is manageable and not very expensive."
"There is a community edition available and the price of the commercial offering is reasonable."
"You only pay for what you use."
"We are using the free version and intend to upgrade."
"The price of Elastic Enterprise is very, very competitive."
"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."
"The pricing structure depends on the scalability steps."
"I rate Elastic Search's pricing an eight out of ten."
"We use the free version for some logs, but not extensive use."
"An X-Pack license is more affordable than Splunk."
"The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
881,757 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
10%
Manufacturing Company
10%
Government
7%
Financial Services Firm
12%
Computer Software Company
12%
Manufacturing Company
9%
Retailer
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?
On the subject of pricing, Elastic Search is very cost-efficient. You can host it on-premises, which would incur zero cost, or take it as a SaaS-based service, where the expenses remain minimal.
What needs improvement with ELK Elasticsearch?
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 inde...
 

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: February 2026.
881,757 professionals have used our research since 2012.