# AWS Compliance

AWS Compliance is the practice of meeting and demonstrating applicable regulatory, industry, and contractual requirements for workloads running on AWS.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/aws-compliance

> Compliance in AWS combines AWS-provided infrastructure assurances with customer responsibilities for data, applications, configurations, and operating procedures. Engineers must identify applicable requirements, verify service and geographic scope, implement controls, and retain evidence rather than assume that using AWS makes a workload compliant.

Practice exams covering AWS Compliance: [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist), [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of AWS Compliance

AWS compliance depends on clearly assigned responsibilities, verified assurance scope, appropriate controls, and ongoing evidence that applicable requirements are met.

1. **Shared compliance responsibilities**: Separate AWS-operated controls from customer-operated controls using the shared responsibility model and service documentation. Managed services reduce some operational responsibilities but do not remove obligations for access, data protection, and application design.
2. **Authoritative documentation and evidence**: Use AWS compliance program pages and service scope information to establish applicability, then obtain relevant reports and agreements through AWS Artifact. Distinguish implementation guidance from independent assurance evidence.
3. **Service-specific compliance scope**: Verify that each selected service, Region, and relevant capability is covered by the required program. Record the scope and reporting period rather than treating AWS-wide assurances as universal coverage.
4. **Geographic and industry requirements**: Translate applicable privacy, residency, healthcare, and payment requirements into architecture and operating controls. Include backups, replication, logging, and contractual arrangements in the assessment.
5. **Governance and control ownership**: Assign owners to requirements, document policies, and define how exceptions are approved and reviewed. Apply account-level boundaries and deployment restrictions where they support those policies.
6. **Continuous assessment**: Collect configuration history and activity logs, evaluate controls regularly, and track remediation. Automated results support assessments but do not replace review of procedural controls or formal compliance determinations.

## Cloud services for AWS Compliance

AWS Artifact supplies AWS-side assurance documents, while AWS Organizations helps establish preventive governance boundaries across accounts. AWS Config evaluates supported resource configurations against chosen rules, and AWS CloudTrail records activity that can explain who changed resources and when. Together, these services support control implementation, monitoring, and evidence collection. Engineers must still select controls that match applicable obligations, configure service coverage and retention, investigate failures, and document procedural requirements. None of these services independently determines whether an entire workload or organization satisfies a law, contract, or compliance framework.

- **[AWS Artifact](https://blowstack.com/tools/cloud-services-hub/aws-artifact)**: Provides access to AWS compliance reports and certain agreements used in due diligence and audits. It supplies evidence about AWS controls, not certification of a customer's workload.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: Records supported resource configurations and evaluates them against configured rules. Configuration history and conformance packs help engineers detect deviations and assemble evidence for technical controls.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Records AWS account activity, including API actions, to support accountability, investigations, and audit evidence. Configure the required event coverage, retention, and log protection; default event history is not a complete long-term audit solution.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: Supports multi-account governance through organizational structure and policies such as service control policies. SCPs limit available permissions in affected member accounts; they do not grant permissions or establish compliance by themselves.

## AWS Compliance exam questions

Real practice exam questions on AWS Compliance, with the correct answer and its explanation.

### Question 1 (AIB-C01 (beta))

**Question:**

A retailer adds an AI assistant to help analysts investigate disputed card payments on AWS. The payment system sends full payment card numbers to the assistant, and the assistant's diagnostic logs retain copies of these requests. The retailer has verified that the selected AWS services are covered by AWS's PCI DSS assessment. The project sponsor argues that the assistant can therefore remain outside the retailer's payment-card compliance assessment. What should the AI governance lead require before approving production use?

**Correct answer:** Have payment-card compliance specialists assess the assistant's end-to-end data flows, determine the affected scope, and verify customer-owned controls and evidence before approval.

**Explanation:** Compliance scope follows the actual processing and retention of cardholder data. The retailer must assess the AI components and diagnostic logs, identify its responsibilities, and demonstrate that applicable controls operate effectively. AWS's assessment supplies infrastructure assurance but does not replace this workload assessment.

### Question 2 (SOA-C03)

**Question:**

A company runs production Linux EC2 instances that are managed nodes in AWS Systems Manager. A custom patch baseline defines the approved security updates and is registered to the instances' patch group. All instances are online daily.

The security team requires refreshed, per-instance compliance results every day that identify missing approved patches. Production policy permits patch installation only during a separately managed monthly maintenance window. The daily assessment must not install patches or restart instances.

Which solution meets these requirements with the least operational overhead?

**Correct answer:** Create a daily Systems Manager maintenance window with a Run Command task that runs AWS-RunPatchBaseline with Operation set to Scan. Target the production patch group and review the results in Systems Manager Compliance.

**Explanation:** The Scan operation evaluates installed patches against the applicable patch baseline and reports patch compliance without installing patches or restarting instances. Scheduling it daily refreshes the per-instance results while leaving installation to the monthly process.

### Question 3 (AIF-C01)

**Question:**

A financial services company is reviewing a generative AI application hosted on AWS. Before approving deployment, its risk team requires independent audit evidence about AWS-operated infrastructure controls, including physical access to data centers. The team will assess the company's application controls separately. Which approach best meets the risk team's requirement?

**Correct answer:** Use AWS Artifact to download applicable AWS SOC reports and review the infrastructure controls covered by those reports.

**Explanation:** AWS Artifact provides on-demand access to AWS compliance documentation, including independent SOC audit reports. Applicable reports help the team assess AWS-operated infrastructure controls without replacing the company's separate assessment of its application controls.

### Question 4 (SAA-C03)

**Question:**

A healthcare provider plans to process electronic protected health information (ePHI) in a new AWS account. The proposed architecture uses several managed services, but the provider has not verified their HIPAA eligibility. The account is not covered by an AWS Business Associate Addendum (BAA), and no ePHI has been uploaded. The provider must satisfy the applicable AWS contractual prerequisites and establish controls for its own handling of ePHI before launch. Which approach should a solutions architect recommend?

**Correct answer:** Verify that every service handling ePHI is HIPAA eligible and follow its applicable usage requirements. Accept an AWS BAA through AWS Artifact that covers the account, and implement and document the provider's required security controls.

**Explanation:** This approach addresses service eligibility, contractual coverage, and customer responsibilities. The BAA must cover the account before ePHI is processed, and using eligible services does not eliminate the provider's responsibility for secure configurations, access management, data handling, and compliance evidence.

### Question 5 (CLF-C02)

**Question:**

A company completes a review of its AWS workload using AWS-provided architectural questions and best practices. The review identifies no high-risk issues. A project manager proposes submitting the review results as proof that the workload meets all applicable regulatory requirements. How should a cloud practitioner respond?

**Correct answer:** The AWS Well-Architected Framework review supports architectural risk assessment, but the company must separately verify applicable compliance requirements and retain supporting evidence.

**Explanation:** A Well-Architected review evaluates a workload against architectural best practices and helps guide improvements. It does not certify regulatory compliance or replace evidence that required controls are implemented and operating.

## Practice AWS Compliance in a full exam

Questions on AWS Compliance in each practice exam, with every answer option and an explanation for each:

- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 29 questions
- [AIB-C01 (beta)](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist): 12 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 3 questions
- [AIF-C01](https://blowstack.com/practice-exams/aws-certified-ai-practitioner): 2 questions

## What is AWS Compliance

AWS Compliance concerns both satisfying requirements and demonstrating that the required controls operate effectively. Requirements can come from laws, industry standards, contracts, and internal policies. Examples include payment-card security requirements under PCI DSS, obligations for protected health information under HIPAA, and privacy obligations under the GDPR. These are not interchangeable: a certification, audit report, contractual agreement, and legal obligation each serve different purposes.

The shared responsibility model determines which controls AWS operates and which the customer must implement. AWS is responsible for security of the cloud, including physical facilities and underlying infrastructure. Customers remain responsible for security in the cloud, with responsibilities varying by service. For example, customers manage guest operating-system patching on Amazon EC2, while a managed database service transfers more infrastructure operations to AWS. In either case, customers must still address their own access permissions, data handling, and application behavior.

Start an assessment by classifying data, identifying applicable obligations, and mapping requirements to technical and organizational controls. Record who owns each control and what evidence demonstrates it. Governance provides the decision-making structure through policies, account boundaries, approvals, and exception handling. Compliance evaluates whether relevant requirements are met; governance establishes how the organization manages those responsibilities.

AWS publishes several resources for this work. The AWS Compliance website describes compliance programs, and AWS Services in Scope by Compliance Program identifies services covered by particular assurance programs. AWS Artifact provides access to AWS compliance reports and certain agreements, including applicable business associate agreements. Security whitepapers, the AWS shared responsibility model, service security documentation, and the AWS Well-Architected Framework Security Pillar explain responsibilities and implementation practices. Guidance documents help engineers design controls, but they do not replace audit evidence or establish that a customer workload is compliant.

Compliance coverage must be checked for the actual services, Regions, and features being used. A service included in one compliance program is not necessarily included in another, and coverage should not be assumed to extend to every deployment location or service capability. Review the scope and reporting period of relevant reports. AWS certifications and attestations can support an assessment of inherited infrastructure controls, but they do not automatically certify customer applications.

Geography and industry affect architecture choices. A healthcare workload handling protected health information may require an AWS business associate agreement, HIPAA-eligible services, and customer-operated safeguards. A payment application must define its cardholder-data environment and implement applicable PCI DSS controls. A workload subject to residency or transfer restrictions requires examination of primary storage, replicas, backups, logs, support arrangements, and relevant service behavior. Selecting a Region alone does not establish compliance with every privacy or cross-border transfer obligation.

In practice, engineers combine preventive controls with continuous evidence collection. They might restrict resource deployment through organizational policies, evaluate encryption settings with configuration rules, and retain API activity records for investigations and audits. These measures introduce costs, operational overhead, and sometimes constraints on service selection or disaster recovery. Automated checks reduce repetitive work, but a passing dashboard only proves that the configured checks passed. Compliance also depends on people, processes, evidence quality, and periodic reassessment as workloads and requirements change.

## Learn AWS Compliance in lessons

8 short lessons on AWS Compliance in 5 certification courses.

- AIB-C01 (beta): AWS Compliance: regulatory controls for AI workloads (Premium), https://app.blowstack.com/lessons/aws-compliance-regulatory-controls-for-ai-workloads-aib-c01
- SOA-C03: AWS Compliance: translating requirements into controls (Premium), https://app.blowstack.com/lessons/aws-compliance-translating-requirements-into-controls-soa-c03
- AIF-C01: AWS Compliance: infrastructure assurances (Premium), https://app.blowstack.com/lessons/aws-compliance-infrastructure-assurances-aif-c01
- SAA-C03: AWS Compliance: mapping requirements to workload controls (Premium), https://app.blowstack.com/lessons/aws-compliance-mapping-requirements-to-workload-controls-saa-c03
- CLF-C02: AWS Compliance: controls and evidence (Premium), https://app.blowstack.com/lessons/aws-compliance-controls-and-evidence-clf-c02
- AIF-C01: AWS Compliance versus Security (Premium), https://app.blowstack.com/lessons/aws-compliance-versus-security-aif-c01
