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 2 of 4
How responsibility shifts with the service you choose
1 min read
The line between AWS and the customer is not fixed. It moves with how much of the stack a service hides. Amazon EC2 is infrastructure as a service, so the customer manages the guest operating system, the installed software and the security groups on each instance. On more abstracted services, AWS runs more of the stack.
| Service | AWS also runs | The customer still owns |
|---|---|---|
| Amazon EC2 | Only the hosts, hardware and virtualization | Guest OS patches, installed software, security groups, data, access |
| Amazon RDS | The database host and its operating system | Network access, database logins, the choice to encrypt |
| AWS Lambda | Servers and, with a managed runtime, runtime patching | Function code, data, permissions |
The rule to remember: the more managed the service, the less the customer patches, yet the customer never hands over its data, its code or the decision about who may use them. Example: a team moves a reporting database from a self-managed engine on Amazon EC2 to Amazon RDS.
Before, it patched the server operating system itself. After the move that job is gone, but the team still decides which networks can reach the database, who gets a login, and whether snapshots are encrypted.
Check yourself
1. A company rebuilds an application that ran on Amazon EC2 as AWS Lambda functions using a managed runtime. Which statement describes how its security responsibility changes?
2. A team moves a self-managed database from Amazon EC2 to Amazon RDS. Which security task stops being the team's job after the move?
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 →