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
 

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
Elastic Search
Ranking in Search as a Service
1st
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
65
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (12th), Vector Databases (1st)
 

Mindshare comparison

As of December 2024, in the Search as a Service category, the mindshare of Amazon AWS CloudSearch is 10.6%, down from 12.6% compared to the previous year. The mindshare of Elastic Search is 13.3%, up from 7.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service
 

Featured Reviews

AmrIssa - PeerSpot reviewer
A scalable and fully managed search service with diverse data type support and robust security
We use it as our hosting solution, serving as the backbone for our systems, which include Rubrik and SAP It is remarkably efficient and beneficial. A reboot should be enhanced. There are issues with the VBC collection. I have been working with it for four years. I would rate the stability ten…
Saurav Kumar - PeerSpot reviewer
Provides us with the capability to execute multiple queries according to our requirements
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.

Quotes from Members

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

Pros

"It is remarkably efficient and beneficial."
"The quality of the solution is good."
"I've found the solution to be very scalable."
"The best feature is its scalability in that Cloud is always on the fly."
"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."
"CDN service reduces latency when accessing our web application."
"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."
"Elasticsearch includes a graphical user interface (GUI) called Kibana. The GUI features are extremely beneficial to us."
"ELK Elasticsearch is 100% scalable as scalability is built into the design"
"I value the feature that allows me to share the dashboards to different people with different levels of access."
"The solution has good security features. I have been happy with the dashboards and interface."
"The UI is very nice, and performance wise it's quite good too."
"The solution is stable and reliable."
"I like how it allows us to connect to Kafka and get this data in a document format very easily. Elasticsearch is very fast when you do text-based searches of documents. That area is very good, and the search is very good."
"The solution is quite scalable and this is one of its advantages."
 

Cons

"The solution should improve the recovery aspects that it has on offer."
"A reboot should be enhanced."
"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."
"Amazon AWS CloudSearch is highly stable. However, the speed depends on your internet connection."
"Security is a concern but they're working on it."
"AWS CloudSearch's documentation isn't very clear. Also, the on-premise version of the solution is less stable than the cloud version."
"I do not have any suggestions for improvements at this time."
"The price of the solution can be expensive."
"I would rate the stability a seven out of ten. We faced a few issues."
"There are potential improvements based on our client feedback, like unifying the licensing cost structure."
"Elastic Search needs to improve its technical support. It should be customer-friendly and have good support."
"Kibana should be more friendly, especially when building dashboards."
"Elastic Enterprise Search's tech support is good but it could be improved."
"There are challenges with performance management and scalability."
"The real-time search functionality is not operational due to its impact on system resources."
"Its licensing needs to be improved. They don't offer a perpetual license. They want to know how many nodes you will be using, and they ask for an annual subscription. Otherwise, they don't give you permission to use it. Our customers are generally military or police departments or customers without connection to the internet. Therefore, this model is not suitable for us. This subscription-based model is not the best for OEM vendors. Another annoying thing about Elasticsearch is its roadmap. We are developing something, and then they say, "Okay. We have removed that feature in this release," and when we are adapting to that release, they say, "Okay. We have removed that one as well." We don't know what they will remove in the next version. They are not looking for backward compatibility from the customers' perspective. They just remove a feature and say, "Okay. We've removed this one." In terms of new features, it should have an ODBC driver so that you can search and integrate this product with existing BI tools and reporting tools. Currently, you need to go for third parties, such as CData, in order to achieve this. ODBC driver is the most important feature required. Its Community Edition does not have security features. For example, you cannot authenticate with a username and password. It should have security features. They might have put it in the latest release."
 

Pricing and Cost Advice

"Our license costs around $4,000 per month."
"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."
"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."
"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."
"In comparison to IBM and Microsoft, the pricing is more favorable."
"We are using the free open-sourced version of this solution."
"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."
"This product is open-source and can be used free of charge."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"The tool is not expensive. Its licensing costs are yearly."
"we are using a licensed version of the product."
"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 paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
824,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
22%
Financial Services Firm
16%
Manufacturing Company
8%
Comms Service Provider
6%
Computer Software Company
19%
Financial Services Firm
15%
Manufacturing Company
8%
Government
7%
 

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 am not directly involved with pricing or setup costs. While I know a portion is open-source, a paid version might be necessary.
What needs improvement with ELK Elasticsearch?
An improvement would be to have an interface that allows easier navigation and tracing of logs. The current system requires manually inputting dates to verify alerts. A visual timeline that pinpoin...
 

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: December 2024.
824,053 professionals have used our research since 2012.