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

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
7th
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.8
Number of Reviews
69
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (11th), Vector Databases (2nd)
 

Mindshare comparison

As of May 2025, in the Search as a Service category, the mindshare of Amazon AWS CloudSearch is 8.6%, down from 11.8% compared to the previous year. The mindshare of Elastic Search is 15.6%, up from 8.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service
 

Featured Reviews

HarishMahanta - PeerSpot reviewer
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.
Anand_Kumar - PeerSpot reviewer
Captures data from all other sources and becomes a MOM aka monitoring of monitors
Scalability and ROI are the areas they have to improve. Their license terms are based on the number of cores. If you increase the number of cores, it becomes very difficult to manage at a large scale. For example, if I have a $3 million project, I won't sell it because if we're dealing with a 10 TB or 50 TB system, there are a lot of systems and applications to monitor, and I have to make an MOM (Mean of Max) for everything. This is because of the cost impact. Also, when you have horizontal scaling, it's like a multi-story building with only one elevator. You have to run around, and it's not efficient. Even the smallest task becomes difficult. That's the problem with horizontal scaling. They need to improve this because if they increase the cores and adjust the licensing accordingly, it would make more sense.

Quotes from Members

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

Pros

"AWS CloudSearch's best features are good performance under high CPU and memory use, and ease of deployment and scaling."
"The initial setup is straightforward."
"The most valuable feature of Amazon AWS CloudSearch is its ability to receive data quickly. You can access your data easily in a short time."
"It's the best solution for any company. It has a hosting ERP system for any task. AWS is stable. AWS is more flexible and its elastic concept is a new concept. AWS is also very secure. It has many layers of security, like hardware security and software security. This is a big issue."
"Document indexing, text-based search API, and Geospatial searches are all good features."
"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."
"CDN service reduces latency when accessing our web application."
"The quality of the solution is good."
"The most valuable feature of Elasticsearch is its convenience in handling unstructured data."
"Helps us to store the data in key value pairs and, based on that, we can produce visualisations in Kibana."
"The most valuable feature of the solution is its utility and usefulness."
"The solution is stable and reliable."
"Gives us a more user-friendly, centralized solution (for those who just needed a quick glance, without being masters of sed and awk) as well as the ability to implement various mechanisms for machine-learning from our logs, and sending alerts for anomalies."
"The most valuable features are the detection and correlation features."
"There's lots of processing power. You can actually just add machines to get more performance if you need to. It's pretty flexible and very easy to add another log. It's not like 'oh, no, it's going to be so much extra data'. That's not a problem for the machine. It can handle it."
"The stability of Elasticsearch was very high, and I would rate it a ten."
 

Cons

"Amazon AWS CloudSearch is highly stable. However, the speed depends on your internet connection."
"Latlon data type only supports single value per document. All other types support multiple values. We faced issues with this because we had scenarios where, for each document, we needed to store multiple latlon values for different geographical locations."
"Regarding the period of propagation on CDN servers, sometimes we update photos or files and we don't see the update instantly. We need to wait for sometime."
"The solution should improve the recovery aspects that it has on offer."
"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."
"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."
"I do not have any suggestions for improvements at this time."
"We'd like to see more database features."
"I have not been using the solution for many years to know exactly the improvements needed. However, they could simplify how the YML files have to be structured properly."
"Elasticsearch could be improved in terms of scalability."
"The real-time search functionality is not operational due to its impact on system resources."
"Dashboards could be more flexible, and it would be nice to provide more drill-down capabilities."
"Something that could be improved is better integrations with Cortex and QRadar, for example."
"Elastic Enterprise Search's tech support is good but it could be improved."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
"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."
 

Pricing and Cost Advice

"I'm not sure how much we pay a year. It might be around $30,000 a year."
"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."
"Our license costs around $4,000 per month."
"We chose AWS because of its cost and stability."
"Amazon AWS CloudSearch charging is based on how many resources you consume or and the solution is known to be a bit expensive."
"There was no license needed to use this solution."
"​The pricing and license model are clear: node-based model."
"The tool is not expensive. Its licensing costs are yearly."
"The solution is less expensive than Stackdriver and Grafana."
"The pricing structure depends on the scalability steps."
"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."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"We use the free version for some logs, but not extensive use."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
850,760 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
23%
Financial Services Firm
17%
Manufacturing Company
10%
University
6%
Computer Software Company
17%
Financial Services Firm
15%
Government
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon AWS CloudSearch?
In comparison to IBM and Microsoft, the pricing is more favorable. I would rate it eight out of ten.
What needs improvement with Amazon AWS CloudSearch?
A reboot should be enhanced. There are issues with the VBC collection.
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?
I don't know about pricing. That is dealt with by the sales team and our account team. I was not involved with that.
What needs improvement with ELK Elasticsearch?
I found an issue with Elasticsearch in terms of aggregation. They are good, yet the rules written for this are not really good. There is a maximum of 10,000 entries, so the limitation means that if...
 

Comparisons

 

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 2025.
850,760 professionals have used our research since 2012.