Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/41 ▾
  1. 1.Cloud Concepts: Benefits & Economics0/4
    1. The six advantages of cloud computing
    2. Elasticity, scalability, agility, high availability and global reach
    3. Cloud economics: fixed versus variable cost and total cost of ownership
    4. Licensing, rightsizing and automation
  2. 2.Cloud Concepts: Well-Architected & Migration0/5
    1. The six pillars of the Well-Architected Framework
    2. Pillar trade-offs and the AWS Well-Architected Tool
    3. The AWS Cloud Adoption Framework: outcomes, perspectives and phases
    4. Migration strategies: the 7 Rs
    5. AWS migration services and tools
  3. 3.Security: Shared Responsibility & Compliance0/4
    1. Security of the cloud and security in the cloud
    2. How responsibility shifts with the service you choose
    3. Compliance reports, programs and where data lives
    4. Encryption, keys and audit records
  4. 4.Security: IAM & Access Management0/4
    1. The root user and sign-in credentials
    2. IAM users, user groups and roles
    3. Policies, deny rules and least privilege
    4. Federation, IAM Identity Center, Amazon Cognito and secrets
  5. 5.Security: Services & Resources0/4
    1. Blocking web attacks and DDoS: AWS WAF, AWS Shield and AWS Firewall Manager
    2. Detecting threats, flaws and sensitive data: GuardDuty, Inspector and Macie
    3. Collecting, investigating and advising: Security Hub, Detective and Trusted Advisor
    4. AWS Marketplace and where to find security help
  6. 6.Technology: Deployment & Global Infrastructure0/4
    1. Ways to access AWS: console, CLI, SDKs and APIs
    2. Deployment tools and cloud deployment models
    3. Regions, Availability Zones and high availability
    4. Multiple Regions, data residency and edge services
  7. 7.Technology: Compute & Networking0/4
    1. Amazon EC2 instance types, auto scaling and load balancers
    2. Containers, serverless compute, Lightsail and AWS Batch
    3. Inside a VPC: subnets, gateways, security groups and network ACLs
    4. Route 53 and connecting networks to AWS
  8. 8.Technology: Databases & Storage0/4
    1. Relational databases: Amazon RDS, Aurora and databases on EC2
    2. NoSQL, in-memory and graph databases, plus database migration
    3. Amazon S3 object storage, storage classes and lifecycle policies
    4. Block and file storage, Storage Gateway, AWS Backup and disaster recovery
  9. 9.Technology: AI, Analytics & Other Services0/4
    1. AI and machine learning services: pre-trained services and SageMaker AI
    2. Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
    3. Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
    4. Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
  10. 10.Billing, Pricing & Support0/4
    1. EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
    2. Data transfer costs, consolidated billing and cost allocation tags
    3. Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
    4. AWS Support plans, Trusted Advisor, AWS Health and where to get help
Saved in this browser. Move it to another device →
← Security: Shared Responsibility & Compliance

Chapter 3 · Lesson 3 of 4

Compliance reports, programs and where data lives

1 min read

AWS Artifact is the self-service portal for downloading AWS's own compliance documents on demand, such as SOC reports, PCI reports and ISO certifications, and for managing agreements such as the Business Associate Addendum (BAA) used with HIPAA workloads.

These reports describe AWS's controls. They can support a customer's audit as evidence about the cloud layer, but the customer must still show that its own company and its own use of AWS comply.

ProgramWhat it is about
PCI DSSPayment card data
HIPAAUS health information law, with no formal certification
FedRAMPUS government use of cloud services

To check whether a service may be used for a program, look it up on the AWS Services in Scope by Compliance Program page. Scope is set per service and per program, so one covered service says nothing about the others.

Data location is the customer's call: it picks the Region that stores its content, and AWS says it will not move that content out without agreement, except as needed to provide a service the customer started or to obey the law.

Example: a clinic confirms that the two services it plans to use are listed for HIPAA, accepts the BAA in AWS Artifact, and keeps its files in a Region its policy allows.

Check yourself

1. A retailer downloads AWS's PCI DSS report from AWS Artifact and plans to give it to its auditor as proof that the retailer itself is PCI DSS compliant. What is the problem with this plan?

2. A company that handles health records wants to check whether a particular AWS service is covered for HIPAA workloads before using it. Where should it look?

Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, AWS Shared Responsibility Model, AWS Services in Scope by Compliance Program

AWS Cloud Practitioner cheat sheet: every key fact on one page →