Amazon Kendra Reviews

We use it for search, enterprise search, text content generation, and content writing. These are some very high-level use cases that we are exploring with different services.

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.

There are some token limits. We cannot ask questions with more than 30 tokens. Access cannot be more than 200 tokens. And the token is also, like, one point. Then views are very hard limits, and it is difficult to increase them. So that is one part Kendra can improve on.

I have been working with Amazon Kendra for five to six months. 

We have good use cases where stability is everything. So it's a stable solution.

So far, we don't have that complexity with scalability. At least I have not come across it. 

The only scalability challenge I've noticed is the limitation in the number of tokens. Amazon Kendra can only return 100 search results, and that the maximum length of a query is 30 words.Otherwise, it does a decent job.

The customer service and support are good because it depends upon the support plan. So we have 24/7 telephonic support available. So for us, the support experience is good. So, customer-wise, it depends on that also.  With 24/7 support, we ensure that SLAs are met, and we are very proactive in that regard. 

If the support are not able to solve an issue, they'll involve someone else from their internal team, and they'll ensure that you get the right answer all the time.

Positive

The installation is particularly an AWS service. So no challenges. Simply, all are very well-versed with AWS. Not a challenge for us. So, it's a good process.

The deployment depends on the use case and can be done in less than a month. 

For maintenance, it is in AWS service, it has all integration in place. So not a challenge. So if you are going with a multi-cloud approach, then there can be some challenges. But it has all the required logging information, maintenance, and all those concepts are in place. Therefore, it is relatively easy, but if you talk about a multi-cloud environment, it could have difficulties.

The pricing falls in the medium range. The cost depends on the size of your use case because it has a fixed cost, not a variable. The licensing is on a monthly basis.

There are no extra costs. Only the service pack is required.

I have worked with Google and Azure. For me, all these solutions are equivalent; there's nothing like one is significantly better than the others. Because it depends upon the end customer and their approach.

It all depends on the use case and what the user wants to achieve. There are multiple solutions available, even within AWS. It depends on the specific use case and how the end customer is going to utilize it. 

Kendra gives you the flexibility and capability to search intelligently, which is its strength. However, in the broader context, it depends on various factors. If we focus on the search part, I would rate it around eight out of ten. There are certain limitations in Kendra.

This solution helps in the search for relevant documents. Similar to Google Search on public information, Kendra can help you do the search in your enterprise document repository. If you have a set of documents in your organization, and you want to perform a search and find documents that correspond to your query, then Kendra can provide the top results or a summary from the document content based on your query. We are service integrators and provide consulting services for different enterprise organizations in US.

Until recently, there wasn't an out-of-the-box service in the market for enterprise documents like Kendra. It also provides flexibility to tune the relevance and ranking of results, so that iteratively it can improve the accuracy of results.

In terms of improvement, cost is high on the list because this is a very expensive product. The solution could also be improved if the time for indexing documents could be reduced and it could be made incremental in nature where you don't need to reindex every document whenever new documents get added to the repository. It would be helpful if the process could be simplified, it's a pain point from the user perspective.

I've been using this solution for about four months. 

This is a stable solution. 

This is a very scalable solution and we'll continue to recommend it to our customers. 

The initial setup is quite straightforward, but from the end user's experience it could be simplified, so that any power user can also go ahead and start using it. Indexing the documents is the time consuming aspect of deployment and it's generally where people struggle. It can take up to two or three hours depending on the size of the document repository. We implement ourselves, it doesn't require any specialization for installation, because these things can be done on Amazon Console.

This is a pay per use solution. The calculation depends heavily on the number of documents, and the time we spend using that index.

This is a really, really expensive solution making the adoption of it very difficult at the enterprise level.

I would rate this solution a seven out of 10, mainly due to the high cost.