AWS AI Services
LLM + GenAI
- Amazon Q + Quicksight Implementation on top of existing data sources in AWS like S3 / RDS, etc
- Amazon Bedrock for end to end GenAI capabilities
- Amazon Bedrock - RAG Implementation for internal knowledge bases
- ChatGPT Wrapper for logging all things -> integrate it in buildpiper
Machine Learning
- Amazon SageMaker - Build, Train, and Deploy Machine Learning Models at Scale
- Amazon Comprehend - Discover Insights and Relationships in Text
- Amazon Lex - Build Voice and Text Chatbots
- Amazon Polly - Turn Text into Lifelike Speech
- Amazon Rekognition - Analyze Image and Video. Extract information and insights from your images and videos (ex - objects or persons in an image)
- Amazon Machine Learning - Machine Learning for Developers
- Amazon Translate - Natural and Fluent Language Translation
- Amazon Transcribe - Automatic Speech Recognition (Speech to text)
- Amazon Personalize - recommendations and intelligent user segmentation at scale
- Amazon Augmented AI - Human review of ML models
- AWS DeepLens - Deep Learning Enabled Video Camera
- AWS Deep Learning AMIs - Quickly Start Deep Learning on EC2
- Apache MXNet on AWS - Scalable, High-performance Deep Learning
- TensorFlow on AWS - Open-source Machine Intelligence Library
- Amazon Textract - Easily extract printed text, handwriting, and data from virtually any document
- Amazon Kendra - Enterprise search service
- AWS Fraud Detector - Fraud detection in payments or loyalty services
Amazon Kendra
Find answers faster with intelligent enterprise search powered by machine learning
Amazon Kendra GenAI Index is a new index in Kendra designed for retrieval-augmented generation (RAG) and intelligent search to help enterprises build digital assistants and intelligent search experiences more efficiently and effectively. This index offers high retrieval accuracy, leveraging advanced semantic models and the latest information retrieval technologies. It can be integrated with Bedrock Knowledge Bases and other Bedrock tools to create RAG-powered digital assistants, or used with Q Business for a fully managed digital assistant solution. Kendra GenAI Index addresses common challenges in building retrievers for GenAI assistants, including data ingestion, model selection, and integration with various GenAI tools. Its features include a managed retriever with high semantic accuracy, a hybrid index combining vector and keyword search, pre-optimized parameters, connectors to a variety of enterprise data sources, and metadata-based user permissions filtering.
Amazon Comprehend
Highly accurate intelligent search service powered by machine learning
- Quickly implement a unified search experience across multiple structured and unstructured content repositories.
- Use natural language processing (NLP) to get highly accurate answers without the need for machine learning (ML) expertise.
- Fine-tune your search results based on content attributes, freshness, user behavior, and more.
- Deliver ML-powered instant answers, FAQs, and document ranking as a fully managed service.
Amazon Comprehend vs Amazon Kendra
Dimension | Comprehend | Kendra |
---|---|---|
Goal | Insight extraction, analysis, classification of text. Useful in pipelines, decision making, analytics. | Information retrieval / search: enabling users to ask questions and get relevant documents/snippets. |
Input vs output | Raw text → labels/entities/topics/sentiment etc. You feed text; it processes it. | A collection of documents, indexed ahead of time → searchable. You query. |
Custom vs general | Supports custom: entity recognition, classification, topic modeling etc. tailored to domain. | The search index can be enriched/customized (metadata, synonyms, domain optimization) but the core is about retrieving relevant content, not deeply analyzing every new document unless configured. |
Latency / usage pattern | Often used in pipelines (batch or real-time for individual documents). E.g. as documents arrive. | Often used in applications with interactive queries by users. |
Scalability considerations | Scales for analyzing large volumes of text. Costs based on text processed, custom model training, etc. | Costs depend on size/number of indices, connectors, frequency of queries, updates. Also, keeping indices up to date. |
Integration | Can feed Comprehend outputs into other services (e.g. metadata for search). | Can integrate with Comprehend for enriching the search index. For example, extract entities via Comprehend, attach them as metadata in Kendra to filter or better rank. |
When to use each
- Use Comprehend when you need to analyze text: extract insights, perform sentiment, detect entities, classify documents, discover topics. Good for analytics, monitoring, compliance, content understanding.
- Use Kendra when you want users to search documents (intranet, knowledge base, FAQs etc.) with good precision — retrieving relevant docs or passages, handling varied data sources, enabling filters/facets, making search “smart.”
How they can be used together
They aren’t mutually exclusive. In fact there are patterns where you use Comprehend to enhance Kendra’s search effectiveness:
- Metadata enrichment: Use Comprehend to extract entities, key phrases, classify documents etc., then attach those as metadata to docs before indexing into Kendra. Then Kendra’s filters/facets/relevance boosting can use that metadata.
- Search tuning: Enriched metadata lets Kendra return better results (e.g. filter by entity extracted by Comprehend).
- Complex pipelines: For example, process scanned PDFs via Textract → extract entities/classify with Comprehend → feed into Kendra for search and retrieval.