Study guide
7.6 Data Foundation Services: S3, Glue, OpenSearch, and Quick Sight
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.6 Data Foundation Services: S3, Glue, OpenSearch, and Quick Sight
Key Takeaways Explain This Topic AI
AI service selection depends on data foundations: storage, cataloging, transformation, search, analytics, permissions, and monitoring.
Amazon S3 commonly serves as durable object storage for data lakes, documents, training data, model artifacts, and retrieval sources.
AWS Glue and Lake Formation help organize, catalog, transform, and govern data so AI and analytics teams can use it responsibly.
Amazon OpenSearch Service can support search and vector search patterns, while Amazon Quick Sight supports business intelligence and analytics experiences.
Practitioners should evaluate data quality, lineage, sensitivity, ownership, freshness, and access before approving an AI service.
Last updated: October 2026
Data foundations before AI decisions
A model or managed AI service can only be as useful as the data and workflow around it. AWS AI Practitioner candidates should recognize the supporting data services that appear around AI solutions. Amazon S3, AWS Glue, Lake Formation, Amazon OpenSearch Service, Amazon Quick Sight, Redshift, and EMR are not all AI services, but they shape whether AI can be built, governed, searched, and measured responsibly.
Amazon S3 is often the durable storage layer. Organizations use S3 for data lakes, raw files, curated datasets, document repositories, logs, images, transcripts, model artifacts, and retrieval sources. The practitioner should ask how buckets are organized, who owns the data, whether encryption is configured, what lifecycle rules apply, whether sensitive data is present, and how access is controlled with IAM, bucket policies, and related governance tools.
AWS Glue helps with data integration, cataloging, and transformation. The Glue Data Catalog can help teams discover tables and metadata. ETL jobs and crawlers can support analytics and ML preparation workflows. A practitioner does not need to implement Glue jobs for this exam target, but should know that messy data rarely becomes useful to AI without cataloging, cleaning, and transformation. Glue is part of the path from raw storage to usable data.
Lake Formation is often discussed with data lake governance. It can help manage permissions and access to data in a lake-centered architecture. If an AI application retrieves from a data lake, the access design matters. Users should not receive answers based on data they are not authorized to view. Data lake permissions, identity, tags, and auditability are important before AI systems are connected to broad sources.
Amazon OpenSearch Service supports search and analytics workloads and can support vector search patterns used in some RAG applications. A vector store is not the same as a foundation model. It stores representations that help retrieve relevant content. The practitioner should ask what data will be indexed, how often it updates, how permissions are enforced, how retrieval quality is measured, and whether a managed service such as Bedrock Knowledge Bases can reduce integration work.
Amazon Quick Sight (formerly Amazon QuickSight, now a feature of Amazon Quick) supports interactive dashboards and business intelligence. It helps organizations report trends, inspect metrics, and make decisions from data. Quick Sight may also appear around AI projects as the place where usage, quality, adoption, and business outcomes are reported. The practitioner should separate analytics from AI generation. A dashboard that explains sales trends is not automatically an ML model, even if it supports an AI initiative.
Data need AWS service to recognize AI relevance
Store raw and curated objects Amazon S3 Source documents, datasets, artifacts, logs, and data lake storage.
Catalog and transform data AWS Glue Makes data discoverable and usable for analytics or ML preparation.
Govern data lake access Lake Formation Helps align permissions with sensitive data and user access boundaries.
Search text or vectors Amazon OpenSearch Service Supports retrieval, search, and vector search patterns for applications.
Visualize metrics and outcomes Amazon Quick Sight Reports adoption, quality, cost, and business impact around AI workflows.
Analyze warehouse or big data Redshift or EMR Supports analytics foundations that may feed AI or ML decisions.
Data quality should be reviewed before service selection. For document AI, are scans readable and document types consistent? For personalization, are user events complete and consented? For custom ML, are labels reliable and current? For RAG, are documents authoritative, deduplicated, chunked well, and kept fresh? A model choice cannot compensate for unowned or untrusted source data.
Security and governance controls belong in the data foundation. Sensitive data in S3 might need KMS encryption, Macie discovery, CloudTrail logs, bucket access review, retention policies, and incident response plans. Data catalogs and indexes need ownership. If a document is deleted or access is revoked, the AI system should not keep serving stale or unauthorized content from an index.
A practical data readiness checklist:
Identify the system of record and data owner for each source.
Classify sensitivity, retention, residency, and consent requirements.
Check data quality, freshness, duplicates, missing values, and label reliability.
Decide whether data will be extracted, indexed, embedded, transformed, reported, or used for training.
Verify IAM, encryption, audit logs, and least-privilege access before connecting AI services.
Define metrics that show whether the AI project improves a business outcome, not just whether it runs.
The practitioner should also ask whether analytics is enough. If leaders need a dashboard showing claim volume by category, Quick Sight may solve the problem without ML. If users need searchable documents, OpenSearch Service or an existing search portal may be enough. If they need generated answers grounded in those documents, add a foundation model layer with controls. The best design is the one that meets the need with the least unnecessary AI risk.
In Skill Builder practice, pair AI labs with data service labs. Notice where source files live, how permissions are granted, how indexes are built, and how results are monitored. This is the bridge between cloud fundamentals and AI fluency: AWS AI solutions are still cloud systems with storage, network, identity, cost, and governance responsibilities.