Study guide
9.3 Invocation Logging, CloudTrail Auditing & Observability
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.3 Invocation Logging, CloudTrail Auditing & Observability
Key Takeaways Explain This Topic AI
Model invocation logging is optional, Region-scoped, and endpoint-specific.
CloudWatch Logs and S3 are supported destinations, with independent modality controls and S3 handling for large data.
CloudTrail, invocation logs, metrics, and application audit records answer different questions.
Protect payload logs as sensitive data and test retention, redaction, and delivery-failure handling.
Use request IDs and approved metadata to correlate evidence without copying raw content everywhere.
Last updated: September 2026
9.3 Invocation Logging, CloudTrail Auditing & Observability
Amazon Bedrock exposes three complementary evidence sources: CloudWatch service metrics, AWS CloudTrail events, and optional model invocation logging. They answer different questions and none should be described as a complete substitute for the others.
Model invocation logging
Model invocation logging is disabled by default and is configured per account and Region. Current documentation applies it to supported calls through the bedrock-runtime endpoint, including Converse, ConverseStream, InvokeModel, and InvokeModelWithResponseStream. Calls through other endpoint surfaces can have different observability support, so identify the actual endpoint before promising coverage.
The logging configuration can deliver records to CloudWatch Logs, Amazon S3, or both. A record includes invocation metadata and, when the selected modality is enabled, request and response bodies. Large JSON or binary data can be placed in S3 with a reference in the log record. Text, image, embedding, audio, and video delivery controls are independent fields in the current API; availability depends on the request and model.
Disabling a modality prevents that modality's payload from being selected for delivery. Do not invent a named metadata-only product tier or promise a particular record shape without testing the configuration. If privacy policy forbids retaining raw prompts, the strongest pattern is to avoid enabling payload logging for that path or sanitize the request in a trusted layer before it reaches every configured sink. Confirm the produced record with a canary that contains synthetic markers.
Protect the evidence pipeline
Invocation logs can contain personal data, secrets, retrieved passages, tool material, or copyrighted content. Keep destinations in the supported account and Region, restrict the delivery role and readers, encrypt data, block public S3 access, and define lifecycle and deletion behavior. If regulation requires write-once retention, configure and test S3 Object Lock, retention mode, legal holds, and the permissions that can alter them. Calling an ordinary bucket immutable is insufficient.
Monitor the delivery metrics for CloudWatch and S3 success and failure. A successful inference does not prove its optional log was delivered. Alert on sustained delivery failure, test KMS and destination policies, and record the recovery procedure. Control access to queries and exports as carefully as access to the source log.
Use stable requestMetadata fields for approved low-cardinality labels such as team, environment, feature, or experiment. Do not place personal data or credentials in metadata. Request metadata is caller-supplied, is retained only when invocation logging is enabled, and is not itself a cost-allocation tag.
CloudTrail and application evidence
CloudTrail records supported Bedrock API activity. Management events are appropriate for questions such as who changed an agent, Guardrail, Knowledge Base, or logging configuration. Some runtime activity requires data-event configuration or has resource-specific support. CloudTrail records API identity and request context; it is not the service for retaining complete prompt and response payloads.
An application audit record should link an authenticated business request to the Bedrock request ID, model or inference profile, prompt release, Guardrail version, retrieval and tool outcome, and final business action without copying sensitive content by default. Hashes or governed object references can preserve linkage when raw material must live in a more restricted evidence store.
Incident reconstruction
For a suspicious response, identify the endpoint, Region, caller, operation, request ID, model target, release version, and UTC time. Correlate CloudTrail, invocation delivery records, application traces, Guardrail findings, tool audit logs, and CloudWatch metrics. Preserve the minimum authorized evidence and document gaps. A missing payload can be intentional privacy design; a missing delivery event can be an observability failure.
The exam distinction is straightforward: CloudWatch metrics show aggregate service behavior, CloudTrail shows supported API activity and configuration changes, model invocation logging can capture configured inference records, and application logs connect those AWS events to business authorization and outcomes.
Verification drill
Before relying on the audit design, send synthetic canary requests containing unique text, image, and metadata markers. Confirm which records reach CloudWatch Logs and S3, which bodies are inline or referenced, whether disabled modalities are absent, and whether request IDs join correctly to application and CloudTrail evidence. Then simulate a denied destination write or inaccessible KMS key and verify that delivery-failure metrics alert the named owner.
Test retention separately: attempt deletion with ordinary operator permissions, exercise an approved legal-hold path, and confirm lifecycle behavior after the retention period. Finally, run a privacy query that searches for a synthetic sensitive marker. The result should match the documented minimization or masking decision. These checks turn a diagram into auditable evidence.