Question

Difficulty: MediumShared Responsibility Model

A software development company is migrating its monolithic API to a serverless architecture using AWS Lambda. As part of this transition, the security team is defining operational tasks under the AWS Shared Responsibility Model. Which of the following tasks remains the sole responsibility of the customer when deploying code to AWS Lambda?

  1. Configuring the IAM execution roles and resource-based policies that control access to the Lambda functionsAnswer
  2. B
    Managing the host operating systems and physical hardware where the Lambda functions execute
  3. C
    Applying security patches to the Python and Node.js runtimes provided by AWS for the Lambda functions
  4. D
    Submitting support tickets to request AWS compliance certificates for the infrastructure hosting the Lambda service

Answer

Configuring the IAM execution roles and resource-based policies that control access to the Lambda functions
For serverless services like AWS Lambda, AWS manages the underlying physical infrastructure, virtualization layer, operating systems, and runtimes. The customer is responsible for writing secure application code and managing access control, which includes defining IAM execution roles and configuring resource-based policies to govern function access.

Step-by-Step Solution

1
Analyze the service model of AWS Lambda
AWS Lambda is a serverless (PaaS/managed) compute service.
Understanding the service type helps define the boundary of responsibility; serverless services shift more infrastructure management tasks (like OS patching and runtime maintenance) to AWS.
2
Differentiate between customer and AWS responsibilities for Lambda
AWS manages the physical security, hardware, virtualization layer, operating system, and runtime. The customer manages application code, data, and access permissions (IAM).
This allows identifying which of the options represents a task that is managed by the customer ('security in the cloud') vs AWS ('security of the cloud').

Key Concept

Shared Responsibility Model for Serverless Services
Rate this question