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

Amazon AWS CloudSearch vs Elastic Search comparison

 

Comparison Buyer's Guide

Executive Summary

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 AWS CloudSearch
Ranking in Search as a Service
9th
Average Rating
8.4
Number of Reviews
12
Ranking in other categories
No ranking in other categories
Elastic Search
Ranking in Search as a Service
1st
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
96
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Vector Databases (2nd)
 

Mindshare comparison

As of May 2026, in the Search as a Service category, the mindshare of Amazon AWS CloudSearch is 5.3%, down from 8.5% compared to the previous year. The mindshare of Elastic Search is 17.6%, up from 15.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Elastic Search17.6%
Amazon AWS CloudSearch5.3%
Other77.1%
Search as a Service
 

Featured Reviews

HarishMahanta - PeerSpot reviewer
Sr PeopleSoft Consultant at People Tech
A reasonably priced solution that provides scalability, stability, reliability, and security
In terms of what needs improvement, I would say that it needs to keep its cost competitive in the market, especially in comparison to other clouds. Let's say we have various clouds in the market, like Google Cloud, Oracle Cloud, and AWS Cloud. However, security-wise, I don't think AWS is bad. It's good only, especially in comparison to Oracle Cloud, if you really use Oracle, while also considering the fact that PeopleSoft is an Oracle product. AWS is a separate cloud, and Oracle has its own cloud. If you are in a new PeopleSoft and Oracle and you are using a third-party cloud, it means it is not easy since we can't think it is easy. I mean, if you are using Oracle products and you are using Oracle Cloud, it will be easier for you. However, it has a cost in comparison to AWS. Oracle Cloud is too costly. According to region, we segregate because it depends on the organization's strength. Let's say your organization has 1,000 customers. In that case, on a daily basis, let's say one customer was released or discontinued using the product. Then, you have to remove the solution. However, if you use Oracle Cloud, that space will remain there. In the case of AWS, they will immediately cut down their space, meaning in terms of reuse ability, it will reduce the cost. In our case, AWS is the best in the market, actually. We have various clouds like Google Cloud and Microsoft Azure Cloud, the features of which are very different. There are a lot of features in AWS Cloud since I am not in the market providing service on the products. I am just using that tool to access our clients' database and deliver our day-to-day service. I interact with the clients regarding their issues, whatever they are facing. There is this one kind of interface we use to access things because they are in AWS Cloud. If your customer is in Oracle Cloud, then there will be a different approach to accessing it. In our case, we can use AWS or Oracle, so it doesn't matter to us.
reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.

Quotes from Members

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

Pros

"The quality of the solution is good."
"There are plenty of services from the database, with many valuable features, good scalability and agility, okay pricing, good solution quality, strong optimization, and customization that can work with any other cloud platforms."
"Storage of photos and files which can be accessed anyplace, anytime, extremely quickly."
"It's the best solution for any company; it has a hosting ERP system for any task, AWS is stable, more flexible with its elastic concept, and also very secure with many layers of hardware and software security."
"We were able to build the core search functionality using this product."
"The best feature is its scalability in that Cloud is always on the fly."
"The most valuable feature of Amazon AWS CloudSearch is the cloud aspect. I do not need to have the physical infrastructure, everything is in the cloud."
"It is remarkably efficient and beneficial."
"The solution is valuable for log analytics."
"The most valuable features are the data store and the X-pack extension."
"This is a very rich product, and it's got a very wide functionality, and a wide range of functionalities which I don't see in the other products, especially not in the cheaper ones."
"Elasticsearch includes a graphical user interface (GUI) called Kibana, and the GUI features are extremely beneficial to us."
"The most valuable features are its user-friendly interface and seamless navigation."
"Elastic Search has excellent features, particularly its scalability and speed."
"I have found the sort capability of Elastic very useful for allowing us to find the information we need very quickly."
"I would recommend Elastic Search to other people who want to have fast search in their applications."
 

Cons

"Amazon AWS CloudSearch is highly stable. However, the speed depends on your internet connection."
"The solution should improve the recovery aspects that it has on offer."
"Amazon AWS CloudSearch is highly stable. However, the speed depends on your internet connection."
"We'd like to see more database features."
"Index cleanup is sometimes painful. No easy way to clean indexes or a bulk of documents. Full indexing or regeneration of entire indexes sometimes gets stuck. In one instance, we had to delete the entire index and re-create it."
"In terms of what needs improvement, I would say that it needs to keep its cost competitive in the market, especially in comparison to other clouds."
"Maybe they are common in Egypt, but you should make a request on Amazon to create a function to monitor CPU performance, memory, and files. It is very difficult in AWS. I would tell them it should be simple, just drag and drop. I think they could develop this option so we can drag and drop to monitor performance of the processor and memory."
"The solution should improve the recovery aspects that it has on offer."
"I found an issue with Elasticsearch in terms of aggregation. They are good, yet the rules written for this are not really good."
"Both the graph feature and the reporting feature are a little bit lacking. The alerting also needs to be improved."
"Elastic Enterprise Search can improve by adding some kind of search that can be used out of the box without too much struggle with configuration. With every kind of search engine, there is some kind of special function that you need to do. A simple out-of-the-box search would be useful."
"There is a lack of technical people to develop, implement and optimize equipment operation and web queries."
"From the UI point of view, we are using most probably Kibana, and I think they can do much better than that."
"There are a few things that did not work for us. When doing a search in a bigger setup, with a huge amount of data where there are several things coming in, it has to be on top of the index that we search."
"Technical support should be faster."
"Elastic Enterprise Search could improve its SSL integration easier. We should not need to go to the back-end servers to do configuration, we should be able to do it on the GUI."
 

Pricing and Cost Advice

"On a scale of one to ten, where one point is cheap, and ten points are expensive, I rate the pricing as medium or reasonable."
"In comparison to IBM and Microsoft, the pricing is more favorable."
"Amazon AWS CloudSearch charging is based on how many resources you consume or and the solution is known to be a bit expensive."
"We chose AWS because of its cost and stability."
"I'm not sure how much we pay a year. It might be around $30,000 a year."
"There was no license needed to use this solution."
"Our license costs around $4,000 per month."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"We are using the open-sourced version."
"This product is open-source and can be used free of charge."
"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."
"The tool is an open-source product."
"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."
"It can be expensive."
"We are using the free version and intend to upgrade."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
10%
Manufacturing Company
10%
Financial Services Firm
6%
Media Company
6%
Financial Services Firm
12%
Computer Software Company
9%
Manufacturing Company
9%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise6
By reviewers
Company SizeCount
Small Business39
Midsize Enterprise12
Large Enterprise47
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for ELK Elasticsearch?
When it comes to pricing, I think we had to pay AWS approximately 1,000 to 1,200 per month for the overall stack. I am not quite certain about how much Elastic Search costs specifically because I w...
What needs improvement with ELK Elasticsearch?
Elastic Search has many features, including Kibana and Logstash, which we regularly use. However, one downside in our product is cost, as it can be expensive when maintaining multiple shards and in...
What is your primary use case for ELK Elasticsearch?
As a developer, I use Elastic Search in developing one of my applications, basically integrating the back-end with Elastic Search. Our main use case for Elastic Search is for Logstash, which is a s...
 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

SmugMug
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 AWS CloudSearch vs. Elastic Search and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.