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

Amazon AWS CloudSearch vs Amazon Elasticsearch Service 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
5th
Average Rating
8.4
Number of Reviews
12
Ranking in other categories
No ranking in other categories
Amazon Elasticsearch Service
Ranking in Search as a Service
3rd
Average Rating
8.2
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2025, in the Search as a Service category, the mindshare of Amazon AWS CloudSearch is 9.3%, down from 11.8% compared to the previous year. The mindshare of Amazon Elasticsearch Service is 9.5%, down from 18.7% 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.
Surjit Choudhury - PeerSpot reviewer
A solution beneficial for the streaming of data that needs to improve its configuration part
Not for all the projects I saw, but most of the projects were using Elasticsearch, which is very common. In my case, I have faced two scenarios with the solution. Other than that, generic solutions like SNS, SQS, and Lambda are some of the very generic tools we are using. Regarding what I would like to see improved in the solution, I would say that, basically, the configuration part is an area with a shortcoming. We have a DevOps person, so all these things are configured in the Terraform through the Terraform script we use. The DevOps team used to take care of it. To run the process or run the services and how to use the services are the parts for which we are using the solution. Some upgradation is required on the configuration side so that we can get to use it. In that case, I have to check on that area with the DevOps.

Quotes from Members

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

Pros

"It will remain alive in the market. The solution will be stable in the market."
"The best feature is its scalability in that Cloud is always on the fly."
"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."
"I've found the solution to be very scalable."
"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."
"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."
"It is remarkably efficient and beneficial."
"The initial set up is very easy...We really appreciate Amazon!"
"In case there is a failure, Elastic manages everything well, and there no major downtime."
"It enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs."
"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."
"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'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 stability of the product is good."
 

Cons

"AWS CloudSearch's documentation isn't very clear. Also, the on-premise version of the solution is less stable than the cloud version."
"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."
"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."
"A reboot should be enhanced."
"The price of the solution can be expensive."
"The solution should improve the recovery aspects that it has on offer."
"Security is a concern but they're working on it."
"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"The configuration should be more straightforward because we had to select a lot of things."
"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 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."
"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."
 

Pricing and Cost Advice

"Our license costs around $4,000 per month."
"There was no license needed to use this solution."
"We chose AWS because of its cost and stability."
"In comparison to IBM and Microsoft, the pricing is more favorable."
"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."
"Amazon AWS CloudSearch charging is based on how many resources you consume or and the solution is known to be a bit expensive."
"I'm not sure how much we pay a year. It might be around $30,000 a year."
"There is a community edition available and the price of the commercial offering is reasonable."
"You only pay for what you use."
"Compared to other cloud platforms, it is manageable and not very expensive."
"The solution is not expensive, but priced averagely, I will say."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
842,388 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
24%
Financial Services Firm
17%
Manufacturing Company
8%
University
5%
Financial Services Firm
21%
Computer Software Company
13%
Manufacturing Company
12%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

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 Amazon Elasticsearch Service?
It enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs.
What is your experience regarding pricing and costs for Amazon Elasticsearch Service?
The solution is not expensive, but priced averagely, I will say. Regarding the pricing part based on the use cases, we used to sometimes see or do some of the costing parts also in that case. Depar...
What needs improvement with Amazon Elasticsearch Service?
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...
 

Overview

 

Sample Customers

SmugMug
VIDCOIN, Wyng, Yellow New Zealand, zipMoney, Cimri, Siemens, Unbabel
Find out what your peers are saying about Amazon AWS CloudSearch vs. Amazon Elasticsearch Service and other solutions. Updated: March 2025.
842,388 professionals have used our research since 2012.