We performed a comparison between Amazon AWS CloudSearch and Elastic Search based on real PeerSpot user reviews.
Find out in this report how the two Search as a Service solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It is remarkably efficient and beneficial."
"I've found the solution to be very scalable."
"CDN service reduces latency when accessing our web application."
"AWS CloudSearch's best features are good performance under high CPU and memory use, and ease of deployment and scaling."
"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."
"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."
"Document indexing, text-based search API, and Geospatial searches are all good features."
"The initial setup is straightforward."
"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."
"ELK Elasticsearch is 100% scalable as scalability is built into the design"
"The flexibility and the support for diverse languages that it provides for searching the database are most valuable. We can use different languages to query the database."
"It's a stable solution and we have not had any issues."
"The most valuable features are the detection and correlation features."
"The UI is very nice, and performance wise it's quite good too."
"The products comes with REST APIs."
"I really like the visualization that you can do within it. That's really handy. Product-wise, it is a very good and stable product."
"The solution should improve the recovery aspects that it has on offer."
"I do not have any suggestions for improvements at this time."
"I would say that it needs to keep its cost competitive in the market, especially in comparison to other clouds."
"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."
"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."
"Amazon AWS CloudSearch is highly stable. However, the speed depends on your internet connection."
"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."
"Machine learning on search needs improvement."
"It was not possible to use authentication three years back. You needed to buy the product's services for authentication."
"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."
"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)."
"Technical support should be faster."
"Kibana should be more friendly, especially when building dashboards."
"The documentation regarding customization could be better."
"We have an issue with the volume of data that we can handle."
Amazon AWS CloudSearch is ranked 5th in Search as a Service with 12 reviews while Elastic Search is ranked 1st in Search as a Service with 59 reviews. Amazon AWS CloudSearch is rated 8.4, while Elastic Search is rated 8.2. The top reviewer of Amazon AWS CloudSearch writes "A reasonably priced solution that provides scalability, stability, reliability, and security". On the other hand, the top reviewer of Elastic Search writes "Played a crucial role in enhancing our cybersecurity efforts ". Amazon AWS CloudSearch is most compared with Solr, Amazon Kendra, Algolia, Amazon Athena and Azure Search, whereas Elastic Search is most compared with Faiss, Milvus, Pinecone, Azure Search and Coralogix. See our Amazon AWS CloudSearch vs. Elastic Search report.
See our list of best Search as a Service vendors.
We monitor all Search as a Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
