Chapters0/41 ▾
- 1.Cloud Concepts: Benefits & Economics0/4
- 2.Cloud Concepts: Well-Architected & Migration0/5
- 3.Security: Shared Responsibility & Compliance0/4
- 4.Security: IAM & Access Management0/4
- 5.Security: Services & Resources0/4
- 6.Technology: Deployment & Global Infrastructure0/4
- 7.Technology: Compute & Networking0/4
- 8.Technology: Databases & Storage0/4
- 9.Technology: AI, Analytics & Other Services0/4
- AI and machine learning services: pre-trained services and SageMaker AI
- Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
- Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
- Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
- 10.Billing, Pricing & Support0/4
- EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
- Data transfer costs, consolidated billing and cost allocation tags
- Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
- AWS Support plans, Trusted Advisor, AWS Health and where to get help
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 type | Who carries it out | Examples |
|---|---|---|
| Inherited | AWS alone; the customer cites AWS's evidence | Physical and environmental controls at data centers |
| Shared | Each party, in the layer it controls | Patch management, configuration management, awareness and training |
| Customer specific | The customer alone | Protecting 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 →