The AWS Shared Responsibility Model Explained for Cloud Practitioner
Know this topic? Test it on a full CLF-C02 paper
A complete CLF-C02 practice exam: 65 questions in 90 minutes, an explanation on every item and an Exam Coach report that ranks your weakest domains.
AWS-CLF-FULL
Try a free Cloud Practitioner exam
Already have an account? Log in to redeem
AWS is responsible for security of the cloud: the hardware, facilities and global infrastructure. You are responsible for security in the cloud: your data, identities and configuration. The line moves with the service, so on EC2 you patch the guest operating system, and on RDS or Lambda AWS patches it for you.Checked against AWS's published exam guide on 9 November 2026.
In this guide
Who does what
| AWS (of the cloud) | You (in the cloud) |
|---|---|
| Physical data centers and hardware | Your data and who can reach it |
| The host and virtualization layer | IAM users, roles and permissions |
| Global network and facilities | Guest OS patches, on EC2 |
| Managed-service infrastructure | Security groups and network configuration |
How responsibility shifts by service
| Service | AWS handles | You handle |
|---|---|---|
| Amazon EC2 | Hardware and host | Guest OS patches, firewall rules, applications, data |
| Amazon RDS | OS and database engine patching | Database users, network access, data |
| AWS Lambda | OS and runtime | Function code, IAM permissions, data |
| Amazon S3 | Storage infrastructure | Bucket policies, encryption choice, data |
Who is responsible? Common examples
| Situation | Responsible |
|---|---|
| A server fails in an AWS data center | AWS |
| An S3 bucket is accidentally left public | Customer |
| An IAM user has too many permissions | Customer |
| Patching the operating system on EC2 | Customer |
| Patching the engine on Amazon RDS | AWS |
| Deciding whether to encrypt data | Customer |
| Securing the data center's physical doors | AWS |
| Backing up data on an EC2 volume | Customer |
Most public cloud security incidents come from customer configuration, which is why the customer side of this model dominates the questions.
Common misunderstandings
- "AWS backs up my data." Backups are your responsibility, although AWS provides tools such as AWS Backup.
- "Managed means AWS handles security." On RDS, AWS patches the engine, but you still control who can connect and what they can see.
- "Compliance is automatic." AWS provides reports through Artifact, and you remain responsible for your own use of the services.
How the exam words it
| If the question says | Think |
|---|---|
| Security OF the cloud | AWS |
| Security IN the cloud | Customer |
| Guest OS on EC2 | Customer |
| Hypervisor and physical hosts | AWS |
| Patch management, configuration management, training | Shared controls |
| Physical and environmental controls | Inherited controls |
Shared Responsibility Model: practice questions
Five original questions. Each explanation says why the other options fail.
Your free Cloud Practitioner exam code is ready
Sit the full CLF-C02 paper against the real 90-minute clock. Cloud Practitioner is $39 once, lifetime, future versions included.
AWS-CLF-FULL
Redeem the code
Already have an account? Log in to redeem
Frequently asked questions
What is the AWS shared responsibility model?
AWS secures the cloud infrastructure, and the customer secures what they put in the cloud, including data, identities and configuration.
Who is responsible for data encryption in AWS?
The customer decides whether and how to encrypt data, using AWS tools such as KMS.
Does the shared responsibility model change between services?
Yes. On EC2 you manage the guest OS. On managed services such as RDS and Lambda, AWS manages it.