Core lesson 5 of 18Topic: AWS foundations
AWS shared responsibility model: EC2, S3 and ownership in practice
The AWS shared responsibility model separates AWS-managed infrastructure from customer responsibilities such as data and configuration. The boundary changes with the service. Compare an EC2 guest OS with data access in S3, then assign customer-side work to concrete owners in your organization.
Explain how the boundary differs for EC2 and S3, and assign data, access and maintenance work to AWS or an explicit customer-side owner.
Know the roles of IAM, EC2 and S3. This lesson does not certify a contract, legal compliance or the security of a real configuration.
Infrastructure management is not customer configuration
- Chosen service → Responsibility boundaryDo not apply one boundary to all AWS services or uses.
- Responsibility boundary → Organizational ownerA customer responsibility is not evidence that someone has performed it.
- Organizational owner → Work and evidenceAgree on ownership, timing and verification, then perform the work.
- Chosen service
- EC2 and S3 expose different customer-managed layers.
- Responsibility boundary
- Use the service documentation to separate AWS and customer work.
- Organizational owner
- Assign retained work to a specific owner.
- Work and evidence
- Keep relevant evidence of configuration, maintenance and verification.
AWS protects the underlying infrastructure that runs its services. Customers manage their use and configuration according to the chosen service. Even a shared control such as patching has different objects: AWS infrastructure versus a customer’s EC2 guest OS or installed applications.
The customer boundary changes between EC2 and S3
| Layer | Using EC2 | Using S3 |
|---|---|---|
| Physical infrastructure | Managed within the AWS infrastructure boundary | Managed within the AWS infrastructure boundary |
| Guest/service OS | The customer manages the guest OS, including updates and configuration | AWS manages the operating systems within the S3 service |
| Application | The customer manages applications it installs | Management of the customer’s application using S3 remains separate |
| Data and access | The customer manages its data and access configuration | The customer manages its data, access permissions and encryption options |
Worked example: EC2 reads an internal report from S3
| Work | Example owner to assign | Evidence to establish |
|---|---|---|
| Set the report’s audience | The data owner | Approved users, purposes and retention requirements |
| Configure the application’s AWS access | The identity/access administrator | Required actions and targets, configuration and verification |
| Maintain the guest OS and app | Server and application operators | Maintenance policy, applied updates and functional checks |
| Govern stored data | Data and operations owners | Retention, deletion and recovery requirements and verification |
The job titles are illustrative. One person may hold several roles in a small team, but the work still needs clear ownership. The AWS/customer boundary and your organization’s internal assignment table answer different questions.
Choose an option to see the result and explanation.
A configured feature is not the whole operating process
When using encryption, access controls or diagnostic records, identify the objective, configuration owner, verification and response process. A configured feature alone does not demonstrate that the data meets protection or recovery requirements.
Build an ownership-and-evidence table
- List the chosen services, data and users.
- Read each service’s AWS/customer responsibility boundary.
- For retained work, identify its target, owner, timing and evidence.
- Resolve unassigned tasks and missing dependencies.
- Keep the assignments and verification current after changes.
Check, then explain in your own words
- Explain the different OS-management boundaries of EC2 and S3.
- Identify retained work for data and access.
- Translate customer responsibilities into owners and evidence.
Check your understanding: Is assigning something to “the customer” enough to finish ownership planning?
No. Assign who performs and verifies that work within your organization.
The shared model separates AWS and customer work. Prevent operational gaps by assigning targets, owners, timing and evidence, and distinguish a planned task from a completed one.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- AWS shared responsibility modelChecked:
Scope and conditionsResponsibilities vary by selected service and configuration
Used in this lessonInfrastructure management is not customer configuration The customer boundary changes between EC2 and S3 Worked example: EC2 reads an internal report from S3 A configured feature is not the whole operating process