Study guide
3.3 Model Sources: Managed APIs, Open Source, and Custom Models
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
3.3 Model Sources: Managed APIs, Open Source, and Custom Models
Key Takeaways Explain This Topic AI
A model source decision should start with use-case fit, risk, data sensitivity, team skill, cost, latency, customization needs, and operating responsibility.
Managed AWS AI services are often the simplest option when the task matches a known capability such as translation, transcription, document extraction, moderation, personalization, or fraud detection.
Open source and third-party models can add flexibility, but they introduce licensing, security, hosting, patching, evaluation, and governance responsibilities.
Custom models are justified when the business needs domain-specific behavior, proprietary data learning, or control that managed APIs cannot provide.
Last updated: October 2026
Start with the source of capability
When a project says it needs AI, the first architecture decision is often where the model capability should come from. The options include managed AWS AI services, foundation model APIs through Amazon Bedrock, models available through SageMaker JumpStart or other catalogs, open source models that the organization hosts, third-party services, and custom models trained on organization data. The practitioner skill is to understand tradeoffs, not to implement every path.
A managed API is attractive when the task is common and well served by an AWS service. Amazon Translate can translate text. Amazon Transcribe can convert speech to text. Amazon Polly can generate speech. Amazon Textract can extract text and structure from documents. Amazon Comprehend can analyze text for entities, sentiment, key phrases, and related NLP tasks. Amazon Rekognition can analyze images and video. Amazon Personalize can support recommendations.
Amazon Bedrock provides access to foundation models and related capabilities for generative AI use cases.
Managed services reduce the need to collect training data, train models, host infrastructure, and patch model-serving stacks. They still require governance. A practitioner should ask whether the service supports the language, region, data class, latency, volume, accuracy target, and compliance requirements. A service can be technically easy and still be the wrong choice if it sends data through an unapproved workflow or cannot meet business quality requirements.
Model source Best fit Main practitioner concern
Managed AWS AI API Standard task with limited customization needs Confirm service capability, pricing, data handling, and quality
Amazon Bedrock foundation model Generative AI, summarization, Q and A, drafting, agents, RAG Control hallucination, prompt injection, grounding, cost, and safety
SageMaker JumpStart or catalog model Faster start with prebuilt model choices Evaluate license, performance, hosting, and customization needs
Open source model Need transparency, portability, or specialized model choice Own security, licensing, evaluation, patching, and serving
Custom SageMaker model Domain-specific prediction or proprietary learning need Requires ML skills, data readiness, MLOps, monitoring, and cost control
- No ML or rules Deterministic or low-value problem Avoid unnecessary model risk and operating cost
- Managed API judgment
Managed AI services are often strongest for clear, bounded tasks. If a company needs to extract fields from invoices, Textract may be a better first review than training a custom computer vision model. If a support team needs sentiment or entity extraction from tickets, Comprehend may be worth evaluating before custom NLP. If the task is transcription, Transcribe is usually more appropriate than building speech recognition from scratch.
The practitioner should still insist on a proof of fit. Test representative data, not only clean demos. Include edge cases, languages, document formats, accents, image quality, and noisy inputs. Review pricing based on expected volume. Confirm IAM controls, encryption, logging, and retention. If outputs influence customers, money, safety, employment, credit, health, or legal outcomes, add human review and governance.
Open source, marketplace, and custom paths
Open source models can be useful when the organization needs more control, wants to run workloads in its own AWS account, or needs a specialized model not offered as a managed API. That control comes with responsibilities. The team must evaluate licenses, provenance, known vulnerabilities, model weights, dependency updates, hosting cost, scaling, monitoring, and whether the model was trained on appropriate data. A practitioner should not assume open source means free or safe.
Custom models may be justified when the business has proprietary labeled data and a task that managed services cannot solve well. Examples include predicting failure of a specific industrial asset, ranking internal leads based on company-specific behavior, classifying specialized medical coding notes for internal review, or forecasting demand in a unique supply chain. Custom work can create competitive advantage, but it also requires data scientists, ML engineers, security review, MLOps, and ongoing ownership.
SageMaker AI supports custom ML workflows, including notebooks or Studio environments, training jobs, model registry, endpoints, batch transform, monitoring, and pipelines. For a business analyst or product manager, the important question is not how to configure every setting. The question is whether the added control is worth the added responsibility compared with a managed service or a no-code option such as SageMaker Canvas.
Decision workflow for model source
Define the task and risk level.
Check whether a managed AWS AI service already fits the task.
If generative AI is needed, evaluate Amazon Bedrock model choice, grounding, guardrails, and cost.
If managed options are not enough, review SageMaker JumpStart, open source, or marketplace models with licensing and security review.
Choose custom training only when proprietary data, domain behavior, or control requirements justify the lifecycle burden.
Build a pilot with representative data, baseline metrics, human review, and monitoring.
Reject ML if deterministic rules meet the requirement with lower risk.
This workflow helps prevent overbuilding. A team should not train a custom model to translate common customer emails when Translate meets quality, cost, and governance needs. It also should not force a managed API into a domain where the service cannot meet quality or compliance requirements. Service selection is a risk and ownership decision.
Questions to ask before approval
Before approving a model source, ask who owns quality after launch, what happens when the model is wrong, how sensitive data is protected, whether outputs are explainable enough for the decision, what cost grows with usage, and whether the organization can exit or replace the model. For generative AI, add questions about hallucination, prompt injection, grounding, content safety, and user feedback. For custom or open source models, add questions about patching, license obligations, model cards or documentation, vulnerability scanning, and retraining plans.
The right answer is rarely the most complex model. The right answer is the smallest capability source that meets the business goal with acceptable accuracy, safety, cost, governance, and operational responsibility.