We performed a comparison between Amazon AWS CloudSearch and Amazon Kendra 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."AWS CloudSearch's best features are good performance under high CPU and memory use, and ease of deployment and scaling."
"It is remarkably efficient and beneficial."
"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."
"CDN service reduces latency when accessing our web application."
"I've found the solution to be very scalable."
"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."
"The initial setup is straightforward."
"We have good use cases where stability is everything. So it's a stable solution."
"Provides flexibility to tune the relevance and ranking of results."
"Amazon AWS CloudSearch is highly stable. However, the speed depends on your internet connection."
"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."
"A reboot should be enhanced."
"AWS CloudSearch's documentation isn't very clear. Also, the on-premise version of the solution is less stable than the cloud version."
"We'd like to see more database features."
"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."
"I would say that it needs to keep its cost competitive in the market, especially in comparison to other clouds."
"There are some token limits."
"The time it takes for indexing documents could be reduced."
Amazon AWS CloudSearch is ranked 5th in Search as a Service with 12 reviews while Amazon Kendra is ranked 2nd in Search as a Service with 2 reviews. Amazon AWS CloudSearch is rated 8.4, while Amazon Kendra is rated 7.6. 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 Amazon Kendra writes "Kendra has a nice AI built-in, enhancing the search experience and highly stable solution". Amazon AWS CloudSearch is most compared with Solr, Algolia, Amazon Athena, Elastic Search and Azure Search, whereas Amazon Kendra is most compared with Azure Search, Amazon Elasticsearch Service, Elastic Search, Algolia and Solr. See our Amazon AWS CloudSearch vs. Amazon Kendra 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.