No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon AWS CloudSearch vs Amazon Kendra comparison

Why PeerSpot?
 

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
13
Ranking in other categories
No ranking in other categories
Amazon Kendra
Ranking in Search as a Service
8th
Average Rating
7.6
Reviews Sentiment
7.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2026, in the Search as a Service category, the mindshare of Amazon AWS CloudSearch is 5.8%, down from 7.2% compared to the previous year. The mindshare of Amazon Kendra is 6.2%, down from 9.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Amazon AWS CloudSearch5.8%
Amazon Kendra6.2%
Other88.0%
Search as a Service
 

Featured Reviews

HM
Software Developer at ECFY Consulting Private Limited
Search workflows have become faster and our team manages operational records more efficiently
Improvements for Amazon AWS CloudSearch can be made, but I will first start with the biggest improvement. The biggest improvement area is that Amazon AWS CloudSearch feels a little older compared to newer AWS services. The second thing about improvement is the documentation. The documentation could definitely be refreshed with more practical examples and troubleshooting scenarios. During setup, a few indexing issues took longer to diagnose because error messages were pretty generic. Better debugging visibility would reduce trial-and-error work. Monitoring is decent through Amazon CloudWatch, but I would like more detailed search-level diagnostics out of the box. Sometimes it is not obvious why certain queries rank results differently unless you manually test a lot. More transparent query analysis, indexing, and insights would be useful. Logging exists, but deeper visibility would help during optimization.
AM
Architect at IGT Solutions
Kendra has a nice AI built-in, enhancing the search experience and highly stable solution
There are many valuable features. For example, there are many documents that contain a lot of legal information. So we want to understand whether all the documents have the required complaint-related information or not, and whether they are following the standard policies of documentation. We have multiple documents, so we don't know which document has the sought-after information. Therefore, we want to perform an enterprise search on it. So there are a lot of use cases we are trying to build using these newer technologies, specifically Kendra. Moreover, Kendra has AI, which has an upper edge, and that is really helpful. It has a nice AI inbuilt, which improves the search part of it.

Quotes from Members

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

Pros

"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."
"The most valuable feature of Amazon AWS CloudSearch is its ability to receive data quickly, and you can access your data easily in a short time."
"We were able to build the core search functionality using this product."
"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 quality of the solution is good."
"In our case, AWS is the best in the market, actually."
"Amazon AWS CloudSearch is practical and dependable for teams that want managed search without a lot of infrastructure management."
"Until recently, there wasn't an out-of-the-box service in the market for enterprise documents like Kendra."
"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."
 

Cons

"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."
"AWS CloudSearch's documentation isn't very clear. Also, the on-premise version of the solution is less stable than the cloud version."
"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."
"The solution should improve the recovery aspects that it has on offer."
"The price of the solution can be expensive."
"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."
"Amazon's technical support needs to improve as they only solve about half our problems."
"I do not have any suggestions for improvements at this time."
"There are some token limits."
"This is a really, really expensive solution making the adoption of it very difficult at the enterprise level."
"The time it takes for indexing documents could be reduced."
 

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."
"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."
"There was no license needed to use this solution."
"In comparison to IBM and Microsoft, the pricing is more favorable."
"Amazon AWS CloudSearch charging is based on how many resources you consume or and the solution is known to be a bit expensive."
"We chose AWS because of its cost and stability."
"The pricing falls in the medium range."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
911,839 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
12%
Construction Company
11%
Outsourcing Company
10%
Educational Organization
9%
Financial Services Firm
17%
Computer Software Company
14%
Manufacturing Company
13%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise6
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon AWS CloudSearch?
We purchased Amazon AWS CloudSearch through the AWS Marketplace. Pricing was understandable once we estimated indexing volume and query traffic. Though it can grow if you scale instances aggressive...
What needs improvement with Amazon AWS CloudSearch?
Improvements for Amazon AWS CloudSearch can be made, but I will first start with the biggest improvement. The biggest improvement area is that Amazon AWS CloudSearch feels a little older compared t...
What is your primary use case for Amazon AWS CloudSearch?
The main use case for us was to search the operational records from our company databases and perform full-text search across operational records and uploaded documents. We needed something where u...
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

SmugMug
Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Find out what your peers are saying about Amazon AWS CloudSearch vs. Amazon Kendra and other solutions. Updated: August 2026.
911,839 professionals have used our research since 2012.