AWS Builder Center
What Is Cloud Security? The Shared Responsibility Model Explained

What Is Cloud Security? The Shared Responsibility Model Explained

A simple explanation of what AWS secures for you and what you are responsible for securing yourself.

Series: AWS Security 30 Days, 30 Articles Challenge (31 articles)

  1. 2
    What Is Cloud Security? The Shared Responsibility Model Explained This article
This is Day 01 of the 30 Days AWS Security Challenge. Before we touch IAM, encryption, or any of the security tools AWS offers, we need to answer a more basic question: who is actually responsible for keeping your AWS account safe? The answer might surprise you, and getting it wrong is one of the most common ways companies end up in the news for the wrong reasons.

What Does "Cloud Security" Actually Mean?

When people hear "cloud security," they often picture something AWS handles entirely on your behalf, like a security guard watching over a building. That is only half true.
Cloud security is really a partnership. AWS builds and maintains a massive, physically secure infrastructure. You are responsible for how you configure and use it. Think of it less like hiring a security guard and more like renting an apartment in a building with excellent locks on the front door. The building owner secures the entrance, the elevators, and the walls. You still have to lock your own apartment door and decide who gets a key.

The Shared Responsibility Model, Explained Simply

AWS calls this split the Shared Responsibility Model. It is the single most important concept in cloud security, and almost every security mistake people make on AWS traces back to misunderstanding it.
The model splits responsibility into two halves:
  • Security OF the cloud is AWS's job.
  • Security IN the cloud is your job.
That one line is worth memorizing. Everything else in this 30 day series builds on it.

What AWS Handles (Security OF the Cloud)

AWS takes care of the foundation. This includes things you will never see or touch directly:
  • Physical security of data centers (guards, cameras, restricted access)
  • The hardware running your servers, storage, and databases
  • The network infrastructure connecting everything
  • Patching and maintaining the underlying host systems for managed services
In short, AWS makes sure the building itself cannot be broken into. They handle this at a scale and level of rigor that almost no individual company could match on its own. This is genuinely one of the strongest arguments for using the cloud in the first place.

What You Handle (Security IN the Cloud)

Here is where most breaches actually happen, not because AWS failed, but because a customer left something exposed. Your responsibilities include:
  • Configuring your own resources correctly (like S3 buckets, EC2 instances, and databases)
  • Managing who has access through IAM users, groups, and permissions
  • Encrypting your own data and managing your own encryption keys
  • Setting up firewalls and network rules for your specific applications
  • Patching your own operating systems and applications running on EC2
Notice a pattern? Almost everything on your list involves a decision you have to make. AWS gives you the tools. You decide how to use them.

A Real Example: Why This Split Matters

A simple, real example: Amazon S3 is a storage service. AWS is responsible for making sure the physical drives storing your files do not fail or get physically accessed by the wrong person. But if you create an S3 bucket and accidentally set it to "public," that is on you. AWS did not misconfigure anything. You did.
This exact mistake, public S3 buckets holding sensitive data, has caused some of the most widely reported data leaks in the past decade. The infrastructure was never the weak point. The configuration was.
Here is a quick way to check yourself. Open the AWS Management Console, go to S3, and click into any bucket you own. Look at the "Permissions" tab and check the "Block Public Access" settings. If those are turned off and you are not intentionally hosting public content, turn them back on.

How to Check Where You Stand

You do not need to memorize every detail of the shared responsibility model today. You just need to internalize one habit: whenever something in AWS is not working the way you expect, ask yourself whether this is an infrastructure issue (rare, and usually visible on the AWS Service Health Dashboard) or a configuration issue (common, and almost always fixable by you).
A useful mental checklist for any AWS resource you create:
  1. Who can access this by default?
  1. Is that access wider than it needs to be?
  1. Is my data encrypted, and do I control the keys?
  1. Would I be comfortable if this configuration were public knowledge tomorrow?
If you can answer those four questions honestly for every resource you spin up, you are already ahead of a lot of teams.

Key Takeaways

  • Cloud security is shared. AWS secures the cloud infrastructure, you secure what you put in it.
  • Most real world breaches on AWS come from misconfiguration, not from AWS's infrastructure failing.
  • Your main job is controlling access, encrypting data, and configuring resources correctly.
  • Managed services shift more responsibility to AWS, but never all of it.
  • A quick self check habit (who can access this, and is that too wide) prevents most common mistakes.
Tomorrow we get hands on with the tool that controls almost everything on your side of this line: AWS IAM. We will walk through users, groups, and policies, and how they fit together to control who can do what in your account. See you on Day 02.

Series: AWS Security 30 Days, 30 Articles Challenge (31 articles)

  1. 2
    What Is Cloud Security? The Shared Responsibility Model Explained This article
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article