Study guide
9.1 SageMaker Model Cards & AI Governance Frameworks
AWS Certified Generative AI Developer - Professional AIP-C01
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Foundation Model Fundamentals
1.1 AIP-C01 Exam Structure, Logistics & Passing Strategy 1.2 AIP-C01 Scoring & Professional Decision Strategy 1.3 Foundation Model Landscape & Model Selection on Amazon Bedrock 1.4 Model Abstraction, Controlled Switching & Resilience 1.5 Customization Spectrum: Prompting vs RAG vs Fine-Tuning vs Continued Pre-training 1.6 Custom Model Deployment & Lifecycle Management
2 Chapter 2: Bedrock Knowledge Bases & RAG Architectures
2.1 Managed RAG Architecture with Bedrock Knowledge Bases 2.2 Knowledge Source Integration, Synchronization & Freshness 2.3 Data Ingestion, Parsing & Chunking Strategies 2.4 Embedding Models & Vector Representations 2.5 Vector Index Scale, Migration & Retrieval Evaluation 2.6 Vector Database Selection: OpenSearch Serverless vs Aurora pgvector vs Managed Stores 2.7 Vector Store Security, Multi-Tenancy & Connectivity
3 Chapter 3: Advanced Vector Search, Indexing & Data Compliance
3.1 Hybrid Search, Metadata Filtering & Semantic Reranking 3.2 Metadata Filtering, Reranking & Query Transformation 3.3 Fine-Tuning & Continued Pre-Training Data Pipeline Engineering 3.4 Data Validation, Multimodal Processing & Model Formatting 3.5 Data Privacy, Data Residency & Compliance Governance 3.6 Privacy Preservation, Source Lineage & Audit Evidence
4 Chapter 4: Prompt Engineering & Bedrock Runtime APIs
4.1 Advanced Prompt Engineering Techniques & Inference Parameters 4.2 Inference Parameters, Prompt Governance & Regression 4.3 Converse API vs InvokeModel API & Message Formatting 4.4 Tool Calling, FM API Resilience & Model Routing 4.5 Streaming Architectures & Asynchronous Event Processing 4.6 Resilient Streaming, Deployment & Asynchronous Processing
5 Chapter 5: Amazon Bedrock Agents & Tool Integration
5.1 Agentic Architecture, ReAct Reasoning Loops & Orchestration 5.2 Agent Frameworks, MCP & Lifecycle Management 5.3 Action Groups, OpenAPI Schemas & AWS Lambda Integration 5.4 Agent Memory, Session State & Multi-Agent Collaboration Patterns 5.5 Persistent State & Multi-Agent Coordination 5.6 Advanced Agent Prompt Templates & Flow Customization 5.7 Agent Safeguards, Tool Reliability & Cost Control
6 Chapter 6: Workflow Orchestration & Application Integration
6.1 Amazon Bedrock Prompt Flows & Visual Orchestration 6.2 Step Functions Orchestration & Human-in-the-Loop Workflows 6.3 Enterprise Integration: API Gateway, AppSync, and EventBridge 6.4 Hybrid Integration, GenAI Gateways & CI/CD Tooling
7 Chapter 7: AI Safety & Guardrails for Amazon Bedrock
7.1 Guardrails Architecture, Denied Topics & Content Filters 7.2 Content Safety, Defense in Depth & Threat Detection 7.3 Sensitive Information Filters & PII Redaction/Masking 7.4 Contextual Grounding Checks & Hallucination Prevention
8 Chapter 8: Security, Access Control & Network Architecture
8.1 IAM Least Privilege & Resource Policies for Bedrock 8.2 PrivateLink VPC Endpoints & Network Isolation 8.3 Encryption with AWS KMS & Cross-Account Access Patterns
9 Chapter 9: Governance, Auditing & Operational Logging
9.1 SageMaker Model Cards & AI Governance Frameworks 9.2 Lineage, Fairness, Transparency & Continuous Governance 9.3 Invocation Logging, CloudTrail Auditing & Observability 9.4 Responsible AI, Bias Mitigation & Red Teaming Methodologies
10 Chapter 10: Performance, Throughput & Cost Optimization
10.1 On-Demand vs Provisioned Throughput & Capacity Planning 10.2 Capacity Measurement, Scaling Patterns & Resilience 10.3 Batch Inference & Bedrock Intelligent Prompt Routing 10.4 Intelligent Prompt Routing & Application Eligibility 10.5 Prompt Caching, Token Optimization & Latency Reduction
11 Chapter 11: Testing, Evaluation & Troubleshooting GenAI Solutions
11.1 Amazon Bedrock Model Evaluation (Automatic & Human Workflows) 11.2 Human, RAG & Continuous Evaluation 11.3 Evaluation Metrics & RAG Quality Benchmarking (Ragas, ROUGE, BLEU) 11.4 RAG and Agent Performance Evaluation 11.5 CloudWatch Metrics, Throttling & Operational Observability 11.6 Quota Diagnosis, Retry Control & Operational Troubleshooting 11.7 Troubleshooting Common GenAI Failure Modes & Agent Traces 11.8 Prompt Maintenance, Content Handling & Deployment Validation
9.1 SageMaker Model Cards & AI Governance Frameworks
Key Takeaways Explain This Topic AI
The customer governance resource is SageMaker Model Cards, not an invented Bedrock Model Cards resource.
Substantive card edits create new versions, preserving prior governance evidence.
Model cards document controls; they do not enforce runtime authorization, safety, or deployment policy.
Last updated: September 2026
9.1 SageMaker Model Cards & AI Governance Frameworks
Model cards document what a model is, how it was evaluated, where it should be used, and which limitations and controls apply. The customer-managed AWS resource is Amazon SageMaker Model Cards; Amazon Bedrock does not expose a similarly named model-card resource. Bedrock publishes provider information for available models, while a development team that needs its own governed artifact can create a SageMaker Model Card, including for a model that was not trained in SageMaker AI.
What a useful model card records
A card should identify the exact model or deployment target, owner, business purpose, intended users, approved uses, prohibited uses, risk rating, data provenance, evaluation evidence, safety controls, monitoring plan, and review status. For a Bedrock application, custom fields can reference the foundation model ID or inference profile, Prompt Management version, Guardrail version, Knowledge Base, retrieval dataset, tool set, and deployment configuration.
Governance question Evidence to record
What is being approved? Model ID and version, customization artifact, prompt version, retrieval and tool dependencies
What may it do? Intended users, business process, permitted actions, human-review boundaries
What must it not do? Unsupported languages, prohibited decisions, autonomous actions, regulated-data restrictions
- How was it tested? Dataset version, metrics, judge or human-review method, safety and adversarial results
- How is it controlled? IAM role, Guardrail, network boundary, encryption, logging and retention choices
- When is review required? Expiration date, drift trigger, incident trigger, model or data change trigger
Do not claim that a model card itself enforces policy. It is documentation and an approval record. IAM, network policies, Guardrails, workflow gates, and application validation implement controls. The card helps reviewers verify that those controls exist and that their limitations are understood.
SageMaker Model Cards behavior
SageMaker Model Cards integrate with SageMaker Model Registry. When the associated model was created in SageMaker AI, supported details can be populated from the model. A card can also describe a model created elsewhere, but the team supplies the information manually. That makes the resource useful for governing a Bedrock-based solution even though the Bedrock foundation model is not a SageMaker training job.
Model-card versions support auditability. Current SageMaker documentation explains that changing card content other than approval status creates another version, preserving the earlier record. Cards can be exported to PDF for review. The organization should still retain machine-readable evidence and source artifacts; a PDF alone is not a deployment control or a reproducible evaluation.
Approval status should correspond to a defined workflow such as Draft, Pending Review, Approved for Staging, Approved for Production, or Rejected. Separate model quality approval from application approval when retrieval, prompts, and tools materially change behavior. An approved base model does not automatically approve every application that invokes it.
Minimum viable governance record
For a customer-support assistant, the card might identify the selected Bedrock target, approved languages, internal users, prohibited autonomous refunds, retrieval corpus owner, Guardrail version, evaluation dataset, safety thresholds, and requirement for human approval above a refund amount. Attach an evaluation report by controlled S3 URI and record the release owner and next review date.
Avoid vague fields. 'Use responsibly' is not an operational boundary. 'May draft refund recommendations; may not invoke the payment tool; a service agent approves every refund' is testable. Likewise, 'high accuracy' should become a named dataset, metric, threshold, failed-slice review, and date.
When the model target changes, create a new evaluated release and update the card version. When only approval status changes, follow the model-card status workflow. Keep the application deployment record separate enough to show which approved card version was actually active at a given time.
A card for a third-party or Bedrock-hosted model will not auto-populate all details. Supply the provider information, application-specific evaluation, and controls manually, and distinguish provider claims from results the organization verified.
Relationship to Model Registry
Model Registry catalogs deployable model versions and their artifacts, metadata, and approval status. A model card adds structured documentation about purpose, risk, training, evaluation, and limitations. Link them when SageMaker resources are involved, but do not treat them as interchangeable. A Bedrock application can reference its external model target in a card even when no SageMaker model package is deployed.
Model cards should also state who may change approval status and which evidence is mandatory for that transition. Restrict the API accordingly and audit status changes through the organization's change process.