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 1 of 4

Security of the cloud and security in the cloud

1 min read

The AWS shared responsibility model splits security into two layers. AWS is responsible for security of the cloud: the data centers, hardware, network and the virtualization layer that runs beneath every customer instance.

The customer is responsible for security in the cloud: its data, its identities and permissions, its network settings such as security group rules, and any operating system or application it installs.

A quick test is to ask who can actually reach the thing in question. A customer cannot touch a host server's firmware, and AWS does not log in to a customer's guest operating system.

Control typeWho carries it outExamples
InheritedAWS alone; the customer cites AWS's evidencePhysical and environmental controls at data centers
SharedEach party, in the layer it controlsPatch management, configuration management, awareness and training
Customer specificThe customer aloneProtecting the data and traffic of its own application

Shared controls are split by layer, not by percentage. For patching, AWS fixes the infrastructure and the customer patches its guest operating systems and applications. For training, AWS trains AWS employees and each customer trains its own staff.

Example: a hospital's web servers run on Amazon EC2, and a scan finds an outdated library in its application. The hospital must update it. If a flaw were announced in the virtualization layer instead, AWS would fix it with no action from the hospital.

Check yourself

1. An auditor asks a company which type of control it inherits completely from AWS, with nothing for the company to carry out. Which control fits?

2. A compliance manager is documenting patch management as a shared control for workloads on Amazon EC2. Which description of the split is accurate?

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 →