Skip to content

Lesson 03 β€” AWS Shared Responsibility Model

Learning Path

☁️ Phase 2 – AWS Cloud Security

πŸ“˜ Module 01 – AWS Security Foundations


By the end of this lesson, you will be able to:

  • Explain the AWS Shared Responsibility Model.
  • Differentiate between Security of the Cloud and Security in the Cloud.
  • Identify customer and AWS responsibilities for different AWS services.
  • Apply the Shared Responsibility Model to real enterprise scenarios.
  • Avoid common cloud security misconceptions.

πŸ“š Lesson Information

Estimated Time: 2 Hours

Difficulty: Beginner

Prerequisites: Lesson 01 & Lesson 02

Hands-on Lab: Yes

Assignment: Yes


One of the biggest misconceptions in cloud computing is:

β€œSince everything is hosted on AWS, AWS secures everything.”

This is incorrect.

While AWS secures the underlying cloud infrastructure, customers remain responsible for securing their applications, data, identities, operating systems and configurations.

Understanding these responsibilities helps organisations:

  • Reduce security risks
  • Prevent data breaches
  • Meet compliance requirements
  • Build secure cloud architectures
  • Clearly define operational responsibilities

The Shared Responsibility Model defines the division of security responsibilities between AWS and its customers.

AWS manages the security of the cloud.

Customers manage security in the cloud.

Both parties work together to achieve a secure cloud environment.


AWS Shared Responsibility Model
+-------------------------------+
| Customer Responsibility |
|-------------------------------|
| Data |
| Identity & Access |
| Applications |
| Operating System |
| Network Configuration |
| Encryption |
| Security Groups |
| Monitoring |
+-------------------------------+
Security IN the Cloud
────────────────────────────────────────────────────
Security OF the Cloud
+-------------------------------+
| AWS Responsibility |
|-------------------------------|
| Physical Data Centres |
| Hardware |
| Storage Infrastructure |
| Networking Infrastructure |
| Hypervisor |
| Global Infrastructure |
+-------------------------------+

AWS is responsible for protecting the infrastructure that runs AWS services.

Examples include:

  • Physical security
  • Data centre operations
  • HVAC systems
  • Physical networking
  • Fibre infrastructure
  • Global backbone
  • Servers
  • Storage hardware
  • Hypervisors
  • Availability Zones
  • Regions

Customers never manage these components.


Customers are responsible for securing everything they deploy within AWS.

Typical responsibilities include:

  • IAM Users
  • IAM Roles
  • IAM Policies
  • MFA
  • Operating System patches
  • Application security
  • Data encryption
  • Security Groups
  • Network ACLs
  • Secrets
  • Logging
  • Monitoring
  • Backup configuration

CloudNova launches a new web application on Amazon EC2.

Question:

Who is responsible for securing each layer?

Component Responsibility
Physical Server AWS
Data Centre AWS
Hypervisor AWS
EC2 Operating System Customer
Installed Software Customer
Application Code Customer
Database Credentials Customer
IAM Policies Customer
Security Groups Customer

AWS Customer
Physical Infrastructure Guest Operating System
Hypervisor Patching
Hardware Firewall Rules
Availability Applications
Networking Infrastructure IAM
Power & Cooling Encryption

AWS manages:

  • Storage infrastructure
  • Hardware
  • Availability

Customer manages:

  • Bucket Policies
  • IAM
  • Encryption
  • Public Access
  • Object Permissions
  • Lifecycle Policies

AWS manages:

  • Database platform
  • Hardware
  • Operating system
  • Database engine patching

Customer manages:

  • Database users
  • Passwords
  • Security Groups
  • Encryption
  • Database configuration
  • Backup strategy

AWS manages:

  • Runtime
  • Infrastructure
  • Scaling
  • Availability

Customer manages:

  • Function code
  • IAM execution role
  • Secrets
  • Environment variables
  • Logging
  • Third-party libraries

AWS manages:

  • Control Plane

Customer manages:

  • Worker Nodes
  • Kubernetes configuration
  • RBAC
  • Pods
  • Containers
  • Secrets
  • Network Policies

❌ False

Customers are responsible for patching EC2 instances.


❌ False

AWS secures the storage platform.

Customers secure bucket access.


❌ False

Customers create and manage IAM identities.


❌ False

Customers choose encryption options and manage encryption keys where applicable.


CloudNova recently migrated its HR application to AWS.

During a security review, the following issues were identified:

  • EC2 instances have not been patched for six months.
  • An S3 bucket is publicly accessible.
  • IAM users do not have MFA enabled.
  • Security Groups allow unrestricted SSH access.
  • Database passwords are weak.

The CIO asks:

β€œAWS is a secure cloud provider. Why do we still have these issues?”

As the Cloud Security Engineer, explain which issues are AWS’s responsibility and which belong to CloudNova.


πŸ§ͺ Enterprise Mission 01 β€” Review AWS Account Identity

Section titled β€œπŸ§ͺ Enterprise Mission 01 β€” Review AWS Account Identity”

Identify which AWS account you are currently working in.

Verify the AWS CLI:

Terminal window
aws --version

Terminal window
aws sts get-caller-identity

Example output:

{
"UserId": "AIDAXXXXXXXXXXXXX",
"Account": "123456789012",
"Arn": "arn:aws:iam::123456789012:user/student"
}

Record:

  • Account ID
  • IAM User
  • ARN

πŸ§ͺ Enterprise Mission 02 β€” Review IAM Account Summary

Section titled β€œπŸ§ͺ Enterprise Mission 02 β€” Review IAM Account Summary”

Run:

Terminal window
aws iam get-account-summary

Observe:

  • Number of Users
  • Groups
  • Roles
  • MFA Devices
  • Account Settings

Questions:

  • How many IAM users exist?
  • Is MFA configured?
  • How many roles are available?

πŸ§ͺ Enterprise Mission 03 β€” Inspect AWS Resources

Section titled β€œπŸ§ͺ Enterprise Mission 03 β€” Inspect AWS Resources”

List S3 Buckets:

Terminal window
aws s3api list-buckets

List EC2 Instances:

Terminal window
aws ec2 describe-instances

List Lambda Functions:

Terminal window
aws lambda list-functions

List RDS Databases:

Terminal window
aws rds describe-db-instances

Think about:

Who is responsible for securing each resource?


πŸ§ͺ Enterprise Mission 04 β€” Shared Responsibility Exercise

Section titled β€œπŸ§ͺ Enterprise Mission 04 β€” Shared Responsibility Exercise”

Complete the table.

Task AWS Customer
Physical Security βœ…
Patch EC2 Operating System βœ…
Configure IAM βœ…
Replace Failed Hardware βœ…
Configure Security Groups βœ…
Encrypt S3 Data βœ…
Secure Hypervisor βœ…
Create Backups βœ…
Configure MFA βœ…
Manage Application Code βœ…

πŸ§ͺ Enterprise Mission 05 β€” AWS Documentation Review

Section titled β€œπŸ§ͺ Enterprise Mission 05 β€” AWS Documentation Review”

Visit:

https://aws.amazon.com/compliance/shared-responsibility-model/

Read the AWS Shared Responsibility documentation.

Identify:

  • Three AWS responsibilities.
  • Three customer responsibilities.
  • One example where responsibility changes depending on the AWS service.

Managed services reduce operational effort but do not eliminate customer security responsibilities.

For example:

  • AWS patches the underlying RDS operating system.
  • You are still responsible for:
    • Database users
    • Passwords
    • Encryption
    • Security Groups
    • Database backups
    • Data classification

  1. What is the Shared Responsibility Model?
  2. What is Security of the Cloud?
  3. What is Security in the Cloud?
  4. Who patches EC2 operating systems?
  5. Who manages IAM users?
  6. Who secures AWS data centres?
  7. Who secures S3 bucket permissions?
  8. Who configures Security Groups?
  9. Does AWS manage your application code?
  10. Why is the Shared Responsibility Model important?

Prepare a Shared Responsibility Assessment Report for CloudNova Technologies.

Include:

  • Explanation of the Shared Responsibility Model.
  • Security of the Cloud vs Security in the Cloud.
  • Responsibilities for:
    • EC2
    • S3
    • RDS
    • Lambda
    • EKS
  • Common misconceptions.
  • Recommendations for improving CloudNova’s cloud security posture.

Length: 2–3 pages.


After completing this lesson, you should understand:

  • AWS and customers share responsibility for cloud security.
  • AWS secures the infrastructure that runs cloud services.
  • Customers secure everything they deploy and configure within AWS.
  • The level of customer responsibility changes depending on the AWS service model.
  • Understanding this model is essential for designing secure cloud environments and avoiding security gaps.

  • AWS Shared Responsibility Model Documentation
  • AWS Well-Architected Framework – Security Pillar
  • AWS Security Best Practices
  • AWS IAM User Guide
  • AWS Security Blog

➑️ Lesson 04 β€” AWS Security Best Practices