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 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 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
90
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Vector Databases (2nd)
 

Mindshare comparison

As of March 2026, in the Search as a Service category, the mindshare of Amazon OpenSearch Service is 10.3%, up from 9.5% compared to the previous year. The mindshare of Elastic Search is 17.9%, up from 14.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Elastic Search17.9%
Amazon OpenSearch Service10.3%
Other71.8%
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.
Anurag Pal - PeerSpot reviewer
Technical Lead at a consultancy with 10,001+ employees
Search and aggregations have transformed how I manage and visualize complex real estate data
Elastic Search consumes lots of memory. You have to provide the heap size a lot if you want the best out of it. The major problem is when a company wants to use Elastic Search but it is at a startup stage. At a startup stage, there is a lot of funds to consider. However, their use case is that they have to use a pretty significant amount of data. For that, it is very expensive. For example, if you take OLTP-based databases in the current scenario, such as ClickHouse or Iceberg, you can do it on 4GB RAM also. Elastic Search is for analytical records. You have to do the analytics on it. According to me, as far as I have seen, people will start moving from Elastic Search sooner or later. Why? Because it is expensive. Another thing is that there is an open source available for that, such as ClickHouse. Around 2014 and 2012, there was only one competitor at that time, which was Solr. But now, not only is Solr there, but you can take ClickHouse and you have Iceberg also. How are we going to compete with them? There is also a fork of Elastic Search that is OpenSearch. As far as I have seen in lots of articles I am reading, users are using it as the ELK stack for logs and analyzing logs. That is not the exact use case. It can do more than that if used correctly. But as it involves lots of cost, people are shifting from Elastic Search to other sources. When I am talking about pricing, it is not only the server pricing. It is the amount of memory it is using. The pricing is basically the heap Java, which is taking memory. That is the major problem happening here. If we have to run an MVP, a client comes to me and says, "Anurag, we need to do a proof of concept. Can we do it if I can pay a 4GB or 16GB expense?" How can I suggest to them that a minimum of 16GB is needed for Elastic Search so that your proof of concept will be proved? In that case, what I have to suggest from the beginning is to go with Cassandra or at the initial stage, go with PostgreSQL. The problem is the memory it is taking. That is the only thing.

Quotes from Members

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

Pros

"It's actually easier to collaborate since it is already deployed in the AWS cloud itself."
"It enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs."
"It's a good log management platform. In terms of infrastructure management, it's good."
"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."
"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."
"The customer service is excellent, rated nine out of ten."
"The business analytics capabilities are the most important feature it provides."
"In case there is a failure, Elastic manages everything well, and there no major downtime."
"Elastic Search makes handling large data volumes efficient and supports complex search operations."
"We had many reasons to implement Elasticsearch for search term solutions. Elasticsearch products provide enterprise landscape support for different areas of the company."
"The stability of Elasticsearch was very high, and I would rate it a ten."
"The most valuable features are its user-friendly interface and seamless navigation."
"It is easy to scale with the cluster node model.​"
"The solution has good security features. I have been happy with the dashboards and interface."
"The most valuable features are the ease and speed of the setup."
"I appreciate the indexing capabilities and the speed of indexing in their product, which demonstrates how quickly logs are collected and stored."
 

Cons

"As a user, lower prices or reasonable pricing is always better."
"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."
"One improvement I would like to see is support for auto-scaling."
"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."
"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."
"One improvement I would like to see is support for auto-scaling."
"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."
"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."
"The most significant issue I find with Elastic Search is that it gets out of sync, and this has happened in both cases where I have implemented it."
"I would like to see more integration for the solution with different platforms."
"There were also some difficult times with parallel and point-in-time interfaces, so better documentation could help, particularly more example-driven content."
"Elastic Enterprise Search could improve the report templates."
"Ratio aggregation is not supported in this solution."
"The real-time search functionality is not operational due to its impact on system resources."
"To do what we want to do with Elastic Search, the queries can get complex and require a fuller understanding of the DSL."
"It needs email notification, similar to what Logentries has. Because of the notification issue, we moved to Logentries, as it provides a simple way to receive notification whenever a server encounters an error or unexpected conditions (which we have defined using RegEx​)."
 

Pricing and Cost Advice

"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."
"You only pay for what you use."
"The solution is not expensive, but priced averagely, I will say."
"The tool is an open-source product."
"We are using the open-sourced version."
"To access all the features available you require both the open source license and the production license."
"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."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"The basic license is free, but it comes with a lot of features that aren't free. With a gold license, we get active directory integration. With a platinum license, we get alerting."
"The premium license is expensive."
"The price could be better."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
884,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
10%
Computer Software Company
10%
Government
7%
Financial Services Firm
12%
Computer Software Company
11%
Manufacturing Company
10%
Retailer
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 Business38
Midsize Enterprise10
Large Enterprise45
 

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?
From the UI point of view, we are using most probably Kibana, and I think they can do much better than that. That is something they can fine-tune a little bit, and then it will definitely be a good...
 

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: March 2026.
884,873 professionals have used our research since 2012.