Study guide
7.2 Text, Language, Search, and Document AI Services
AWS AI Practitioner Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: AIF-C01 Orientation and Official Source Control
1.1 Credential Scope, Code, and Search Language 1.2 Exam Format, Cost, Score, and Delivery 1.3 Official Exam Guide, Skill Builder, and Practice Workflow 1.4 Target Candidate Boundaries and Out-of-Scope Tasks 1.5 Domain Weights and Study Prioritization 1.6 Exam Policy, Retake, Results, and Recertification
2 Chapter 2: AI/ML Foundations and Use-Case Fit
2.1 AI, ML, Deep Learning, and Core Terminology 2.2 Supervised, Unsupervised, and Reinforcement Learning 2.3 Data Types, Labels, Structure, and Quality 2.4 Inference Patterns: Batch, Real-Time, and Embedded AI 2.5 AI Use-Case Fit and No-AI Decisions 2.6 Classification, Regression, Clustering, Forecasting, and Recommendation 2.7 AI/ML Foundations Case Lab
3 Chapter 3: ML Lifecycle, Metrics, and Practitioner MLOps
3.1 Data Collection, EDA, Preprocessing, and Feature Concepts 3.2 Training, Evaluation, Deployment, and Monitoring Lifecycle 3.3 Model Sources: Managed APIs, Open Source, and Custom Models 3.4 Evaluation Metrics and Business Metrics 3.5 Practitioner MLOps: Repeatability, Monitoring, and Retraining 3.6 SageMaker Lifecycle Service Map 3.7 ML Lifecycle Case Lab
4 Chapter 4: Generative AI Foundations and Inference Concepts
4.1 Foundation Models, LLMs, Transformers, and Modalities 4.2 Tokens, Context Windows, Embeddings, and Vector Search 4.3 Inference Parameters: Temperature, Top-p, and Output Controls 4.4 Hallucination, Grounding, and Context Quality 4.5 GenAI Use-Case Fit and Risk Triage 4.6 Prompt Injection, Data Leakage, and User Input Risk 4.7 Generative AI Foundations Case Lab
5 Chapter 5: Prompting, Model Selection, Customization, and Evaluation
5.1 Prompt Engineering Patterns and Business Quality 5.2 Zero-Shot, Few-Shot, Templates, and Instruction Design 5.3 Model Selection: Capability, Latency, Cost, and Risk 5.4 RAG vs Fine-Tuning vs Prompting vs Custom Models 5.5 Model Evaluation, Human Review, and Red-Team Feedback 5.6 Cost, Performance, and Throughput Decision-Making 5.7 Prompting and Model Selection Case Lab
6 Chapter 6: Amazon Bedrock, RAG, Agents, and Guardrails
6.1 Bedrock Core Concepts, Model Access, and Managed FM Choice 6.2 Knowledge Bases, RAG, Data Sources, and Grounding 6.3 AI Agents, Tools, Orchestration, and Business Workflows 6.4 Guardrails, Content Filters, Denied Topics, and Sensitive Data 6.5 Bedrock Model Evaluation, Monitoring, and Human Feedback 6.6 Bedrock Cost, Latency, Throughput, and Operational Fit 6.7 Bedrock, RAG, and Agents Case Lab
7 Chapter 7: AWS Managed AI/ML Services and SageMaker Map
7.1 Managed AI Services vs Foundation Model Apps vs Custom ML 7.2 Text, Language, Search, and Document AI Services 7.3 Vision, Speech, Contact Center, and Personalization Services 7.4 Amazon Quick, Amazon Q Developer, Kiro, and Practitioner Fit 7.5 SageMaker Canvas, Studio, Clarify, Autopilot, and Data Wrangler 7.6 Data Foundation Services: S3, Glue, OpenSearch, and Quick Sight 7.7 AWS AI Service Selection Case Lab
8 Chapter 8: Responsible AI, Human Review, and Safety
8.1 Fairness, Bias, Transparency, and Explainability 8.2 Privacy, Safety, Human Review, and Accountability 8.3 Guardrails, Clarify, Human Review, and Content Safety Controls 8.4 Responsible AI Risk Registers and Governance Workflows 8.5 Monitoring, Feedback, Drift, and Incident Response 8.6 Responsible AI Case Lab
9 Chapter 9: Security, Compliance, Governance, and Cost Controls
9.1 Shared Responsibility, IAM, and Least Privilege for AI 9.2 Encryption, Secrets, Networking, and Data Privacy 9.3 Prompt Injection, Data Exfiltration, and GenAI Threat Modeling 9.4 Logging, Monitoring, CloudTrail, CloudWatch, and Config 9.5 Compliance: Artifact, Config, Macie, and Policy Evidence 9.6 AI Cost Controls, Pricing, Throughput, and Budget Governance 9.7 Security and Governance Case Lab
10 Chapter 10: Integrated AWS AI Business Scenario Labs
10.1 Customer Support GenAI Assistant Lab 10.2 Document Intelligence and Compliance Review Lab 10.3 Personalization, Forecasting, and Fraud Detection Lab 10.4 Enterprise Search, RAG, and Knowledge Management Lab 10.5 Responsible AI and Security Review Board Lab 10.6 Cost, Performance, and Operations Review Lab 10.7 Full AIF-C01 Business Simulation
11 Chapter 11: Final Review, Exam Readiness, and Recertification
11.1 Final 30-Day AIF-C01 Study Plan 11.2 Official Practice Resources and Weak-Domain Remediation 11.3 90-Minute Exam Timing, Flagging, and Guessing Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Results, Retake, and Recertification Plan 11.6 AWS AI Practitioner Final Mixed Review
7.2 Text, Language, Search, and Document AI Services
Key Takeaways Explain This Topic AI
Amazon Comprehend, Translate, Textract, and OpenSearch Service address different text, document, and search needs; choosing among them starts with the desired output.
Textract is the document extraction fit when the business needs text, forms, tables, or structured fields from files rather than a generated answer.
OpenSearch Service supports search and vector search patterns, while Bedrock Knowledge Bases or Amazon Quick fit generative responses grounded in retrieved content.
Text and document AI workflows need data classification, confidence handling, human review, and privacy controls because documents often contain sensitive information.
A practitioner should ask whether the problem is extraction, classification, translation, search, summarization, or generation before naming a service.
Last updated: October 2026
Text and document service boundaries
Many AWS AI scenarios begin with text, but the word text is not enough to select a service. A support ticket, a scanned contract, a product manual, a call transcript, a multilingual website, and an enterprise policy library are all text-related. They need different outputs. The practitioner should slow the conversation down and ask what the user expects to receive at the end of the workflow.
Amazon Comprehend is a managed natural language processing service. It is a good fit when the business wants to analyze text for insights such as entities, key phrases, language, sentiment, or classification. For example, a support leader might use Comprehend to understand complaint themes in tickets. The output is not a creative answer. It is structured insight that can be routed, counted, searched, or reviewed.
Amazon Translate is the fit when the primary need is language translation. A retailer might translate product descriptions for a regional launch, or an operations team might translate customer messages before routing. Translation quality still needs review for brand, legal, medical, or safety-sensitive content. Translate should not be treated as a complete localization program by itself.
Amazon Textract is the document AI fit when the input is a document and the business needs text, forms, tables, or key fields. It is commonly considered for invoices, receipts, tax forms, insurance forms, and other structured or semi-structured files. The decision is not simply OCR versus AI. The practitioner should ask whether the workflow needs field extraction, confidence thresholds, document type routing, downstream validation, and human review for low-confidence results.
Amazon Kendra is an older AWS enterprise search service. AWS says Kendra is no longer open to new customers and points to Amazon Bedrock Knowledge Bases for similar capabilities, and the AIF-C01 version 1.1 service lists do not name it. For search, recognize Amazon OpenSearch Service, which the exam guide lists among the services that store embeddings in vector databases and which supports k-nearest neighbor (vector) search. When a use case needs a conversational answer grounded in documents, OpenSearch Service or a Bedrock knowledge base can handle retrieval, while Amazon Quick or a Bedrock application provides the generative assistant layer.
Need Likely AWS starting point Boundary to watch
Detect sentiment, entities, key phrases, or language in text Amazon Comprehend It analyzes text; it does not replace workflow design or human judgment.
Translate text between languages Amazon Translate High-risk or brand-sensitive translations still need review.
Extract text, forms, or tables from documents Amazon Textract Validate confidence, document type, and downstream field rules.
Search or retrieve from enterprise knowledge sources Amazon OpenSearch Service or Amazon Bedrock Knowledge Bases Search relevance and permissions matter as much as indexing.
Generate summaries, answers, or drafts Amazon Bedrock or Amazon Quick Add grounding, guardrails, evaluation, and output review where needed.
The most common mistake is to choose a generative model when the business needs extraction. If an accounts payable system needs invoice number, date, vendor, total, and line items, a generated narrative is not the desired output. The team needs reliable extracted fields, confidence handling, validation rules, and exception queues. Textract, combined with workflow logic and a human review queue, is a more appropriate pattern.
The opposite mistake is choosing extraction when the user really wants synthesis. If a product manager asks for a digest of hundreds of customer comments, Comprehend can provide useful signals, but a foundation model might be better for a readable summary. The stronger design may use both: Comprehend for structured classification and Bedrock for summarization, with citations or source samples when decisions are important.
Search decisions require special care. Keyword search, semantic search, and generative answers are not the same user experience. Search returns documents or passages for a person to inspect. A generative answer writes a response that may need grounding and citation. A practitioner should ask whether the user must see source documents, whether permissions differ by user, whether the index must update frequently, and whether hallucination would create material risk.
Documents often contain regulated or sensitive data. Before approving any document AI pipeline, identify PII, financial data, health data, contracts, retention requirements, and cross-border constraints. Use IAM least privilege, encryption, logging decisions, and monitoring. If results flow into another system, decide who can correct extraction errors and whether corrected labels become future training or evaluation data.
A simple review workflow looks like this:
Classify the text or document source and sensitivity.
Choose the desired output: extracted fields, language translation, search result, summary, or generated answer.
Select the managed service that matches that output before considering custom ML.
Define confidence thresholds, fallback behavior, and human review for low-confidence or high-risk cases.
Test with real-looking documents, edge cases, poor scans, unusual languages, and known bad inputs.
Record cost, latency, accuracy, privacy, and operational ownership before expanding.
Skill Builder practice should compare services by output. Review a document extraction lab, a text analytics lab, and a search or generative AI lab if available in your training path. The goal is not to memorize every console screen. It is to recognize which service family solves which text problem and where the business must still supply governance.