Skip to content
Kuza Ndoto Academy

The Shared Responsibility Model

Beginner → IntermediateChapter 1 · Page 5 of 304 min readUpdated 15 Nov 2026

Security in the cloud is a partnership. AWS protects the buildings, hardware and core software that run its services, and you protect what you build and store on top of them. This split is called the shared responsibility model, and misunderstanding it is behind many real cloud data leaks.

Security OF the cloud vs security IN the cloud

AWS sums up the model in two phrases:

  • AWS is responsible for security of the cloud: the physical data centres, guards and cameras, servers, storage hardware, networking equipment, the virtualisation layer and the software that runs its managed services.
  • You are responsible for security in the cloud: your data, who can access it, how your resources are configured, the operating systems you manage, your application code and your network rules.
YOU security IN the cloud Your data and who can see it Applications, IAM users, roles and permissions Guest operating system patches, security groups, network settings Encryption choices for data at rest and in transit AWS security OF the cloud Service software: compute, storage, database, networking Hardware and global infrastructure: Regions, AZs, edge locations
Figure 1. AWS secures the foundation; you secure everything you place on it. The exact line moves depending on the service you use.

The line moves with the service

The more managed a service is, the more AWS handles for you. Compare four services:

TaskEC2 (IaaS)RDS (managed database)Lambda (serverless)S3 (storage)
Physical hardwareAWSAWSAWSAWS
Operating system patchesYouAWSAWSAWS
Database engine patchesYou (if you install one)AWS applies them; you choose the maintenance windown/an/a
Network access rulesYou (security groups)You (security groups, public access setting)You (who may invoke it)You (bucket policies, Block Public Access)
Your data and codeYouYouYouYou
Access permissions (IAM)YouYouYouYou

Notice the last two rows never change. Whatever service you choose, your data and who can access it are always your job.

Shared controls

Some areas are split between both sides, each in its own layer:

  • Patch management: AWS patches its infrastructure; you patch your EC2 operating systems and your app's libraries.
  • Configuration management: AWS configures its hardware; you configure your databases, buckets and networks.
  • Awareness and training: AWS trains its staff; you train yours, for example on spotting phishing emails that try to steal console passwords.

Real-world scenarios

Example

A college in Kisumu stores scanned admission letters in an S3 bucket. A developer, testing quickly, turns off Block Public Access and adds a policy allowing anyone to read objects. Months later a journalist finds the letters, with students' ID numbers, through a search tool. S3 worked exactly as configured, so this is the customer's responsibility. Keeping Block Public Access on and serving files through signed URLs or an authenticated app would have prevented it.

Example

A hard drive fails in an AWS data centre that holds part of a DynamoDB table used by a payments notification service. The service keeps working, because AWS replicates DynamoDB data across Availability Zones. Replacing the drive and securely destroying the old one is AWS's responsibility.

Common mistake

Assuming "it's on AWS, so it's secure". AWS gives you secure building blocks and safe defaults, such as Block Public Access on new buckets and encryption at rest for new S3 objects, but you can switch those defaults off. Most cloud breaches come from customer misconfiguration: public buckets, leaked access keys, SSH open to the whole internet or over-generous permissions.

How AWS helps you with your share

  • IAM and IAM Identity Center control who can do what.
  • AWS CloudTrail records API calls, so you can see who changed what.
  • AWS Config tracks resource settings and flags ones that break your rules.
  • Amazon GuardDuty watches for suspicious activity such as stolen credentials being used.
  • AWS Security Hub gathers findings and checks against best-practice standards.
  • AWS Artifact gives you AWS's own compliance reports for audits.

Key points

  • AWS secures the cloud itself; you secure what you put in it.
  • The more managed the service, the more AWS takes on, but your data, access rules and configuration are always yours.
  • Most cloud breaches are customer misconfigurations, not AWS failures.
  • Use AWS's security tools (IAM, CloudTrail, Config, GuardDuty) to carry out your part.
Up next · New chapter: Security & AccessIAM: Users, Groups, Roles & PoliciesControl who can do what in your AWS account.
→

Tip: use the ← and → keys to move between pages.