Study guide
1.6 Custom Model Deployment & Lifecycle Management
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
1.6 Custom Model Deployment & Lifecycle Management
Key Takeaways Explain This Topic AI
Check the exact model support table before choosing on-demand custom deployment or Provisioned Throughput.
Register data, hyperparameters, model artifacts, evaluations, intended use, owner, and review date.
Retirement must remove traffic and permissions while retaining required audit evidence.
Last updated: September 2026
- 1.6 Custom Model Deployment & Lifecycle Management
- Deployment options are model-specific
Avoid the obsolete rule that every custom Bedrock model must use Provisioned Throughput. Current Amazon Bedrock documentation describes both Provisioned Throughput and custom model deployments for on-demand inference for supported custom models. Imported models can also support on-demand inference. Availability depends on the model, customization type, Region, and current feature-support table.
Provisioned Throughput allocates model units for predictable sustained capacity and is billed while the allocation exists. On-demand custom model deployment charges for use and avoids a fixed provisioned allocation, but supported models and operational characteristics differ. A SageMaker AI endpoint remains appropriate when the team needs container-level control, specialized accelerators, deployment variants, or hosting features not available through the Bedrock path.
The deployment decision must therefore be discovered, not memorized:
Identify the exact custom or imported model artifact.
Check supported inference options and Regions.
Benchmark cold behavior, steady-state latency, quotas, and cost.
Register the version and its evaluation evidence.
Deploy behind a stable application interface.
Canary the new version and retain the previous target for rollback.
Lifecycle management and retirement
Model lifecycle control includes versioning, approvals, rollout, monitoring, rollback, and retirement. Store the base model ID, training data snapshot, hyperparameters or adapter configuration, evaluation report, intended uses, limitations, owner, and expiration review date. SageMaker Model Registry and SageMaker Model Cards can support version and governance records; Bedrock resources and CloudTrail events provide service-specific operational evidence.
Monitor production quality and input drift. A model can remain technically available while becoming unsuitable because user language, policies, or downstream schemas changed. Trigger reevaluation when the base model changes, the retrieval corpus changes materially, a safety incident occurs, or business acceptance metrics deteriorate.
Retirement is an engineering step, not merely deletion. Stop new traffic, preserve required audit evidence, revoke permissions, remove unused endpoints or throughput allocations, update dependent configuration, and verify that rollback or archive obligations are met. The strongest exam answer is the one that treats customization as a governed lifecycle and chooses prompting or RAG when weight changes are unnecessary.
Release record and rollback drill
For each release, create a record containing the immutable artifact identifier, base model, training-data snapshot, code commit, hyperparameters or adapter settings, supported inference path, Region, IAM role, KMS key, evaluation report, and approver. Link the application prompt, Guardrail, retrieval, and tool versions because those dependencies can change observed behavior without changing weights.
Deploy the candidate beside the active version. Shadow traffic can reveal latency and schema behavior without showing outputs to users. A canary then sends a small eligible percentage of live requests and compares quality signals, errors, token use, and business outcomes. Stop automatically on a safety or policy threshold; do not let an average quality gain offset a critical regression.
Practice rollback before the release. Confirm that the prior target remains invokable, configuration propagation is fast enough, state formats remain compatible, and queued jobs retain the intended version. Rollback should restore the complete release configuration, not only the model ARN.
For retirement, drain traffic and jobs, revoke unused roles and keys, remove paid deployments or throughput, update catalogs, and preserve evidence for the required period. A deleted endpoint with an active broad IAM policy is not a complete retirement.
Operational monitoring
Track deployment availability, cold restoration or startup behavior where applicable, latency percentiles, token use, error classes, schema validity, safety interventions, and task quality. Compare these by model version. Training metrics are historical evidence and cannot show production drift.
Set a review trigger for new source data, a model-provider update, a changed business process, an incident, or an expired approval. If reevaluation fails, freeze expansion and route to the approved version while the owner investigates. Version permissions and alarms with the release so a rollback restores observability and access, not only inference.
Ownership and cost cleanup
Assign an owner for the model artifact and every paid inference resource. Tag environments and releases, alarm on unused but billable capacity, and review access after staff or application changes. Lifecycle governance fails when an obsolete deployment remains reachable or a no-commitment allocation continues billing after the experiment.
Before closing the release, verify that documentation names the tested Region and inference option. Support can differ across Regions, and a general product announcement is not evidence that the target deployment path is available in the production account.