Study guide

9.5 Compliance: Artifact, Config, Macie, and Policy Evidence

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

9.5 Compliance: Artifact, Config, Macie, and Policy Evidence

Key Takeaways Explain This Topic AI

AWS Artifact provides on-demand access to AWS compliance reports and certain agreements, which can support vendor risk and audit reviews.

AWS Audit Manager has helped collect evidence against selected frameworks, but it is no longer open to new customers, and evidence collection never makes a workload compliant by itself.

Amazon Macie uses machine learning and pattern matching to discover sensitive data in Amazon S3 and produce findings that can guide remediation.

Compliance evidence for AI should connect policies, controls, owners, logs, resource configurations, data classification, and review cadence.

Practitioners should distinguish AWS responsibility evidence from customer workload evidence.

Last updated: October 2026

Evidence, not assumptions

Compliance conversations often begin with a simple question: can we prove that this AI workload follows policy? A confident verbal answer is not enough. A team needs evidence about AWS service assurances, account configuration, data classification, access control, monitoring, review cadence, and remediation. AI raises the stakes because prompts, retrieved documents, outputs, logs, and model actions can all become part of the compliance story.

AWS Artifact is a portal for AWS compliance reports and certain agreements. It helps organizations review AWS third-party audit reports and service assurance documents when assessing AWS as a cloud provider. A practitioner should understand that Artifact evidence is about AWS controls and agreements. It does not prove that the customer's own AI application is configured correctly, uses approved data, or reviews risky outputs.

AWS Audit Manager automates evidence collection and organizes it against frameworks, but AWS says it is no longer open to new customers; existing customers can continue to use it. For new workloads, recognize the services the AIF-C01 guide lists for governance and compliance (objective 5.2.1): AWS Config, Amazon Inspector, AWS Artifact, AWS CloudTrail, and AWS Trusted Advisor. No evidence tool replaces control ownership. If a policy says model invocation logs must be reviewed weekly, the team still needs a real process and accountable owner.

Amazon Macie helps discover sensitive data in Amazon S3 using machine learning and pattern matching. For AI workloads, Macie can be useful when S3 buckets contain source documents, training datasets, exported logs, transcripts, or generated outputs. Findings can identify personal data or sensitive patterns that should be remediated, restricted, encrypted, excluded from a knowledge base, or reviewed before use.

Evidence source What it supports What it does not prove by itself

AWS Artifact AWS compliance reports and agreements That the customer's AI app is compliant.

AWS Audit Manager (existing customers only) Organized evidence collection against frameworks That every policy exception has been fixed.

Amazon Macie Sensitive data discovery and findings in S3 That all sensitive data in every service is eliminated.

AWS Config Resource configuration history and rule compliance That generated AI answers are accurate or fair.

CloudTrail API activity history That users made correct business decisions.

CloudWatch Logs Operational and application events That log content is safe to retain without access controls.

Policy evidence should be mapped to the AI lifecycle. Before launch, the team should document the use case, approved data sources, model selection rationale, access decisions, guardrails, retention rules, human review requirements, and cost limits. During operation, the team should collect logs, findings, configuration records, review notes, incident tickets, and change approvals. At retirement, the team should document data deletion, access removal, and model or knowledge base decommissioning.

Data classification is a major compliance dependency. A team cannot govern what it has not classified. If a knowledge base indexes S3 documents, the organization should know whether those documents contain public, internal, confidential, regulated, or customer data. Macie can help discover sensitive data in S3, but business owners must decide what findings mean for policy. A bucket with sensitive data might require stricter access, exclusion from AI retrieval, redaction, or a different workflow.

Compliance also includes evidence of review. For a low-risk internal drafting assistant, review may mean periodic access review, cost review, and prompt-quality checks. For a regulated customer workflow, review may include documented approvals, human review of outputs, incident response testing, retention review, and audit trails for model changes. The key is matching evidence depth to business risk.

Audit readiness checklist:

Identify the compliance framework, internal policy, or customer requirement being supported.

Separate AWS provider evidence from customer workload evidence.

Use AWS Artifact for AWS reports and agreements where appropriate.

If the account already uses AWS Audit Manager, keep its evidence current; AWS no longer opens it to new customers.

Use Macie to discover sensitive data in S3 sources, logs, exports, and document stores.

Use CloudTrail, CloudWatch, and Config to support activity, operations, and configuration evidence.

Assign owners for findings, exceptions, remediation deadlines, and review cadence.

Keep evidence linked to the AI use case, not only to generic account controls.

Scenario: a healthcare-adjacent company wants to summarize support tickets with AI. Artifact may support vendor risk review of AWS. Macie can scan S3 buckets that contain ticket exports for sensitive information. AWS Config and CloudTrail can supply configuration and activity evidence for selected controls. The company still needs its own policy about which tickets may be processed, who can view outputs, and whether human review is required.

Scenario: a bank asks whether an AI assistant has compliance evidence. The best answer is not just a screenshot of the assistant. Evidence should include approved use case documentation, IAM permissions, data classification, logs, guardrail settings, source approval, retention settings, and review records. If the assistant can perform actions, evidence should include tool permissions, confirmation rules, and action logs.

Other AWS security services can contribute context. Amazon Inspector can help identify software vulnerabilities in supported workloads that host AI application components. Trusted Advisor can highlight certain account-level best practice checks. These services are useful signals, but they do not replace AI-specific governance around prompts, data, outputs, and model access.

For AIF-C01, remember the boundary. You are not expected to implement a compliance framework. You should recognize which AWS service helps provide provider reports, which helps organize evidence, which helps find sensitive S3 data, and why evidence must be tied back to customer-owned policies and workload controls.