INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Explain how the boundary differs for EC2 and S3, and assign data, access and maintenance work to AWS or an explicit customer-side owner.

Prerequisite

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

From service boundary to an assigned task and evidence
From service boundary to an assigned task and evidence1: Chosen service — Do not apply one boundary to all AWS services or uses. — Responsibility boundary. 2: Responsibility boundary — A customer responsibility is not evidence that someone has performed it. — Organizational owner. 3: Organizational owner — Agree on ownership, timing and verification, then perform the work. — Work and evidence123Chosen serviceResponsibilityboundaryOrganizationalownerWork and evidenceFrom service boundary to an assigned task and evidence1: Chosen service — Do not apply one boundary to all AWS services or uses. — Responsibility boundary. 2: Responsibility boundary — A customer responsibility is not evidence that someone has performed it. — Organizational owner. 3: Organizational owner — Agree on ownership, timing and verification, then perform the work. — Work and evidence123Chosen serviceResponsibilityboundaryOrganizationalownerWork andevidence
  1. Chosen service → Responsibility boundaryDo not apply one boundary to all AWS services or uses.
  2. Responsibility boundary → Organizational ownerA customer responsibility is not evidence that someone has performed it.
  3. 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

The same business data can have a different OS boundary
LayerUsing EC2Using S3
Physical infrastructureManaged within the AWS infrastructure boundaryManaged within the AWS infrastructure boundary
Guest/service OSThe customer manages the guest OS, including updates and configurationAWS manages the operating systems within the S3 service
ApplicationThe customer manages applications it installsManagement of the customer’s application using S3 remains separate
Data and accessThe customer manages its data and access configurationThe customer manages its data, access permissions and encryption options

Worked example: EC2 reads an internal report from S3

Turn retained responsibilities into explicit assignments
WorkExample owner to assignEvidence to establish
Set the report’s audienceThe data ownerApproved users, purposes and retention requirements
Configure the application’s AWS accessThe identity/access administratorRequired actions and targets, configuration and verification
Maintain the guest OS and appServer and application operatorsMaintenance policy, applied updates and functional checks
Govern stored dataData and operations ownersRetention, 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.

An EC2 guest OS needs a patch. Is “AWS runs the infrastructure, so AWS applies it” sufficient?
Read the answer and reason

Answer: Identify the customer-side owner and maintenance method · An EC2 guest OS is distinct from AWS-managed infrastructure. Assign customer-side ownership, an update method and post-update checks.

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

  1. List the chosen services, data and users.
  2. Read each service’s AWS/customer responsibility boundary.
  3. For retained work, identify its target, owner, timing and evidence.
  4. Resolve unassigned tasks and missing dependencies.
  5. Keep the assignments and verification current after changes.

Check, then explain in your own words

  1. Explain the different OS-management boundaries of EC2 and S3.
  2. Identify retained work for data and access.
  3. 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.