AWS Cloud Practitioner (CLF-C02) · Lesson 9 of 26
The Shared Responsibility Model
Explain which security tasks belong to AWS (security of the cloud) and which belong to the customer (security in the cloud), recognize shared controls, and describe how the split shifts between Amazon EC2, Amazon RDS and AWS Lambda.
Tip: turn your phone sideways or use full screen for larger labels.
Captions match the narration word for word. Press Space to play or pause and the arrow keys to change scenes.
Learning objective
Explain which security tasks belong to AWS (security of the cloud) and which belong to the customer (security in the cloud), recognize shared controls, and describe how the split shifts between Amazon EC2, Amazon RDS and AWS Lambda.
Exam mapping
Domain 2: Security and Compliance (30%). Task statement 2.1 in the official exam guide.
Key takeaways
- AWS is responsible for security OF the cloud: the hardware, software, networking and facilities that run AWS services, including physical security, the host operating system and virtualization layer, and the global infrastructure.
- The customer is responsible for security IN the cloud: its data (classification and encryption choices), identity and access management, and the configuration of the services it uses.
- Shared controls apply in both layers, each side in its own context: patch management, configuration management, and awareness and training. Physical and environmental controls are fully inherited from AWS.
- Amazon EC2 (infrastructure as a service): the customer patches the guest operating system, manages installed software and configures security groups.
- Amazon RDS: AWS patches the database engine and the underlying operating system and automates backups; the customer manages database users, network access rules, encryption settings and data.
- AWS Lambda: AWS manages the infrastructure, operating system and managed runtimes; the customer is responsible for its function code, IAM permissions and data. Data and access are always the customer's job.
Exam tips
How the exam asks about this
Questions describe a situation and expect you to recognize the concept behind it.
| If the question mentions… | Think |
|---|---|
| Physical security of data centers; hardware; the hypervisor | AWS (security of the cloud) |
| Patching the guest operating system on Amazon EC2 | Customer |
| Configuring security groups or network access rules | Customer |
| Patching the database engine on Amazon RDS | AWS |
| Managing IAM users, permissions and MFA; encrypting and classifying data | Customer, for every service |
| Patch management, configuration management, awareness and training | Shared controls |
Common traps
- AWS never manages your data or your IAM users and permissions, whatever the service. Even with Lambda or RDS, data and access stay with the customer.
- Security groups are provided by AWS, but configuring their rules is the customer's job. An open security group is a customer mistake, not an AWS failure.
- "Patching" alone doesn't tell you the answer: it's a shared control. Read which layer is being patched: the guest OS on EC2 is the customer's, the RDS database engine or the infrastructure is AWS's.
- Don't assume the line is fixed. The more managed the service (EC2, then RDS, then Lambda), the more AWS takes on.
Practice
Exam-style questions
Answer each one before you open the explanation.
Question 1. Under the AWS shared responsibility model, which task is the responsibility of AWS?
- Patching the guest operating system on Amazon EC2 instances
- Maintaining the physical security of AWS data centers
- Configuring security group rules
- Creating IAM users for employees
Show answer
B. Maintaining the physical security of AWS data centers. Physical security of the facilities is part of security of the cloud, which AWS owns. Patching the guest OS on EC2 is tempting because patching is partly AWS's job, but for EC2 the guest operating system belongs to the customer. Security group rules and IAM users are customer configuration.
Question 2. A company runs its web application on Amazon EC2 instances. Which are the company's responsibilities? (Select TWO.)
- Applying security patches to the guest operating system
- Replacing failed hard drives in the host servers
- Maintaining the virtualization layer
- Configuring the security groups for the instances
- Controlling physical access to the data center
Show answer
A. Applying security patches to the guest operating system and D. Configuring the security groups for the instances. With EC2 (infrastructure as a service), the customer manages the guest OS, including updates and security patches, and configures security groups. Maintaining the virtualization layer is tempting because it sounds like server software, but the hypervisor is part of the infrastructure AWS secures. Hardware and physical access are AWS's too.
Question 3. A company moves its self-managed database from Amazon EC2 to Amazon RDS. Which task does the company no longer need to perform?
- Managing database user accounts and permissions
- Deciding whether to encrypt the data at rest
- Patching the database engine software
- Controlling network access with security groups
Show answer
C. Patching the database engine software. With Amazon RDS, AWS patches the database engine and the operating system underneath it. Encryption is tempting because AWS provides it, but turning it on is still the customer's choice. Database users and security group rules also remain customer responsibilities.
Question 4. Which is an example of a shared control in the AWS shared responsibility model?
- Physical and environmental controls
- Data center power and cooling
- Classifying the customer's data
- Patch management
Show answer
D. Patch management. Patch management is shared: AWS patches the infrastructure and the customer patches its guest operating systems and applications. Physical and environmental controls are tempting because they protect everything, but customers fully inherit them from AWS, as with power and cooling. Classifying data belongs only to the customer.
Question 5. A developer deploys an application as AWS Lambda functions. What is the developer's company responsible for?
- The security of the function code and the IAM permissions it uses
- Patching the operating system that runs the functions
- Maintaining the servers in the data center
- Securing the network hardware between Availability Zones
Show answer
A. The security of the function code and the IAM permissions it uses. With Lambda, AWS manages the infrastructure, the operating system and the managed runtimes; the customer secures its code, the IAM permissions and its data. Patching the operating system is tempting because the customer does it on EC2, but Lambda has no servers for the customer to manage. Servers and network hardware are AWS's.
Transcript
Lesson transcript
The full narration, scene by scene. The captions file contains the same text with timings.
Scene 1 · 0:00
Lesson 9: The Shared Responsibility Model. Welcome to Domain 2, Security and Compliance, which is thirty percent of the scored exam. This lesson covers task 2.1: the AWS shared responsibility model. It's one of the most tested ideas on the whole exam. We'll cover two ideas. First, the split between security of the cloud, which is AWS's job, and security in the cloud, which is yours. Second, how that split moves depending on the service, using Amazon EC2, Amazon RDS and AWS Lambda.
Scene 2 · 0:33
Why a shared model?. In its own data center, our online store secured everything: the data and apps, the servers and network, even the building, the power and the guards. On AWS, the store rents part of a much larger system, so the work is split. AWS takes the lower layers and the store keeps the top ones. The model exists so that both sides know exactly where their duties begin and end, and nobody assumes the other side has it covered.
Scene 3 · 1:07
Security OF the cloud: AWS. Start at the bottom. AWS is responsible for security of the cloud: protecting the infrastructure that runs every AWS service. That means the hardware, software, networking and facilities. Think data center buildings, guards, power and cooling, the servers and network gear, the host operating system and virtualization layer, and the global infrastructure of Regions, Availability Zones and edge locations. Customers can't touch these layers, so they inherit these controls from AWS.
Scene 4 · 1:38
Security IN the cloud: you. Above the line is security in the cloud, and that's the customer's job. The store always owns its data, including how it's classified and encrypted, and who can access it through IAM users, roles and multi-factor authentication. On servers it runs, it patches the guest operating system and configures the firewall, called a security group. How much sits above the line depends on the services the store chooses.
Scene 5 · 2:08
Shared controls. Some controls are shared: the same topic, but each side does it in its own layer. Patch management: AWS patches its infrastructure, and the customer patches its guest operating systems and applications. Configuration management: AWS configures its own devices, and the customer configures its operating systems, databases and apps. Awareness and training: AWS trains its employees, and the store trains its own. Physical and environmental controls, by contrast, are fully inherited from AWS.
Scene 6 · 2:39
Amazon EC2: you manage the most. Now watch the line move. Amazon EC2 is infrastructure as a service. The store gets a virtual server, and everything from the guest operating system up is the store's job: installing OS updates and security patches, the software it adds, and the security group rules. AWS handles the host, the virtualization layer, the hardware and the facilities. With EC2, the line sits low, so the customer carries the most responsibility.
Scene 7 · 3:10
Amazon RDS: the line moves up. Next, the store moves its database to Amazon RDS, a managed database service. Now AWS patches the database engine and the operating system underneath it, during a maintenance window the store can choose, and automates backups. The line moves up. But the store still creates database users and their permissions, sets the network rules in security groups, chooses to turn on encryption, and owns the data itself.
Scene 8 · 3:39
AWS Lambda: the line moves higher. With AWS Lambda, the line moves higher still. Lambda runs the store's code without servers to manage. AWS manages the infrastructure, the operating system and the managed language runtimes, including runtime security updates. The store is responsible for the security of its function code, the IAM permissions the function uses and the data it handles. Notice what never moves across all three services: your data and your access settings are always yours.
Scene 9 · 4:10
Who fixes it?. Let's test it with the store's week. A disk fails in a data center: AWS. The web server on EC2 needs an operating system security patch: the store. A security group lets anyone on the internet reach the database: the store, because security group rules are customer configuration. RDS needs a database engine patch: AWS. A former employee still has an IAM user: the store. A flaw is found in the hypervisor: AWS.
Scene 10 · 4:42
How the exam asks about this. Here's how the exam asks about this. Physical security of data centers: AWS. Patching the guest operating system on EC2: the customer. Configuring security groups: the customer. Patching the database engine on RDS: AWS. Managing IAM users and permissions, and encrypting and classifying data: always the customer. Patch management and awareness and training: shared controls. And watch for questions about how responsibilities shift between EC2, RDS and Lambda.
Scene 11 · 5:12
Recap: the shared responsibility model. To recap: AWS is responsible for security of the cloud, the facilities, hardware, networking and virtualization behind every service. You're responsible for security in the cloud: your data, encryption choices, identities and access, and the settings you control. The more a service is managed, from EC2 to RDS to Lambda, the less you patch, but your data and access are always yours. Next, we'll lock down access itself with IAM essentials: the root user, users and policies.
Sources and accuracy
Checked against AWS documentation and the official CLF-C02 exam guide on October 18, 2026. AWS changes often, so confirm details in the current documentation. Diagrams and numbers in the animation are illustrative.
- Shared Responsibility Model (AWS Compliance)
- Security in Amazon RDS
- Security overview of AWS Lambda: the shared responsibility model
- Shared responsibility model for Lambda runtime management
- CLF-C02 exam guide: Domain 2, Security and Compliance
This free course is independent and isn't affiliated with or endorsed by Amazon Web Services. AWS and AWS Certified Cloud Practitioner are trademarks of Amazon.com, Inc. or its affiliates.
Preparing a team for AWS certification?
I run hands-on AWS training for teams, from Cloud Practitioner basics to architecture, built around your own environment.