The shared responsibility model
When you use AWS, security is a team effort. AWS is responsible for security of the cloud: the buildings, hardware and core software that run its services. You are responsible for security in the cloud: your data, who can access it and how you configure what you use.
This is called the shared responsibility model, and it is one of the most tested ideas in the Cloud Practitioner exam.
What AWS is responsible for
“Security of the cloud” covers everything you cannot touch:
- Physical security of data centers: guards, cameras, access control.
- Hardware: servers, storage devices and network equipment, including safely destroying old disks.
- Global infrastructure: Regions, Availability Zones and edge locations.
- Software that runs AWS services: the virtualization layer and the software behind managed services.
What you are responsible for
“Security in the cloud” covers everything you control:
- Your data, and whether it is encrypted.
- Identity and access: IAM users, roles, permissions and MFA.
- Configuration of the services you use, such as security group rules and bucket access.
- Operating systems and applications you install, for example patching the OS on an EC2 instance.
- Network traffic protection, such as using HTTPS.
The split moves with the service
The more AWS manages for you, the less you have to secure yourself. Compare three ways of running an application:
| Amazon EC2 (virtual server) | Amazon RDS (managed database) | AWS Lambda (serverless) | |
|---|---|---|---|
| Physical hardware, data centers | AWS | AWS | AWS |
| Operating system patching | You | AWS | AWS |
| Database or runtime software patching | You | AWS | AWS |
| Network firewall rules (security groups) | You | You | AWS, unless you connect the function to your own VPC |
| Your code | You | Not applicable | You |
| Data and access permissions | You | You | You |
Notice the last row: your data and who can access it are always your responsibility, no matter how managed the service is.
Shared controls
Some controls apply to both sides, each in its own area:
- Patch management: AWS patches its infrastructure; you patch your guest operating systems and applications.
- Configuration management: AWS configures its devices; you configure your operating systems, databases and applications.
- Awareness and training: AWS trains its staff; you train yours.
AWS also passes some controls on to you through its certifications: for example, the physical and environmental controls of its data centers, which you can show auditors through AWS Artifact.
Putting it together: a data leak
A company stores customer files in an S3 bucket. An employee changes the bucket policy to allow public access, and the files are leaked.
- Whose responsibility was it? The customer’s. S3 is private by default; configuring access is the customer’s job.
- What would have helped? Keeping S3 Block Public Access on, granting least-privilege permissions, and using tools such as AWS Config or Trusted Advisor to flag public buckets.
Common mix-ups
- “AWS encrypts everything, so data is AWS’s job.” Encryption options are provided by AWS, but choosing to use them and managing who can read the data is yours.
- Patching depends on the service. On EC2 you patch the OS; on RDS and Lambda AWS does.
- Managed does not mean “no responsibility”. Even on Lambda you own your code, its permissions and your data.
Check yourself
Who is responsible for patching the operating system of an EC2 instance?
The customer. On EC2 you manage the guest operating system.
Who is responsible for the physical security of the servers that run Amazon RDS?
AWS. Physical security of data centers is always AWS’s responsibility.
Name a control that both AWS and the customer share.
Patch management, configuration management, or awareness and training: each side does it for its own part.
Key takeaways
- AWS: security of the cloud (facilities, hardware, global infrastructure, service software).
- You: security in the cloud (data, access, configuration, your OS and apps).
- The more managed the service, the more AWS handles; your data and access are always yours.
Cloud Study Lab is an independent study site. It is not affiliated with or endorsed by Amazon Web Services. AWS and the names of AWS certifications are trademarks of Amazon.com, Inc. or its affiliates.