Curriculum Overview: AWS Shared Responsibility Model

This curriculum provides a structured pathway to mastering the AWS Shared Responsibility Model (SRM), a cornerstone of the AWS Cloud Practitioner (CLF-C02) certification. Understanding this model is essential for ensuring the security and compliance of any cloud-based workload.

Prerequisites

Before beginning this curriculum, students should have a baseline understanding of the following:

• Cloud Computing Basics: Understanding the difference between On-Premise and Cloud infrastructure.
• AWS Global Infrastructure: Familiarity with Regions, Availability Zones (AZs), and Edge Locations.
• Basic Security Concepts: General knowledge of encryption, firewalls, and user authentication.

---

Module Breakdown

---

Module Objectives

SRM-01: Core Principles

• Distinguish between the two primary parties: AWS (the provider) and the Customer (you).
• Understand the fundamental split: Security OF the Cloud vs. Security IN the Cloud.

SRM-02: AWS Responsibilities

• Identify hardware, software, and networking assets managed by AWS.
• Understand the physical security of data centers and the virtualization layer (Hypervisor).

SRM-03: Customer Responsibilities

• Define the customer's role in securing the Guest Operating System (patches/updates).
• Master the configuration of Security Groups (firewalls) and IAM policies.

SRM-04: Service Variations

• Analyze how responsibility shifts when moving from unmanaged (EC2) to managed (RDS) to serverless (Lambda) services.

---

Success Metrics

To demonstrate mastery of this curriculum, the student must be able to:

1. Correctly Categorize Tasks: Given a list of 20 security tasks, assign them to either AWS or the Customer with 100% accuracy.
2. Explain Shifted Responsibility: Describe why a customer has fewer security tasks when using AWS Lambda compared to Amazon EC2.
3. Define the "Responsibility Formula": $\text{Total Cloud Security} = \text{AWS Security (OF)} + \text{Customer Configuration (IN)}$

[!IMPORTANT] A failure in the customer's portion of the model (e.g., leaving an S3 bucket public) is the primary cause of security breaches in the cloud, not a failure of AWS infrastructure.

---

Real-World Application

Understanding the Shared Responsibility Model is not just for passing an exam; it has direct career implications:

• Risk Management: Architects use the model to determine where security gaps might exist in their specific deployment.
• Compliance & Auditing: When a company needs to meet regulatory standards (like HIPAA or PCI DSS), they must know which controls AWS provides and which they must document themselves.
• Operational Efficiency: By using more "managed" services, companies can shift more responsibility to AWS, allowing their engineers to focus on code rather than patching operating systems.

Comparison: Managed vs Unmanaged Responsibility

[!TIP] Always remember: AWS is responsible for the building, the servers, and the wires. You are responsible for the locks on the doors you create and the data you put inside.