Lambda Deep Dive Pt3 - Security

Security engineering in AWS Lambda.

hello frens, today we are looking at AWS Lambda through

the security perspective. Security is becoming a popular topic with upper management and cloud security engineer roles are abundant and *well* compensated. So it literally pays to know what is in this article.

Required Reading:

AWS Lambda Deep Dive Pt 1

Lambda Deep Dive Pt 2: Execution Environments

AWS Lambda Security

At a high level to understand the security of Lambda lets reference the shared responsibility model for Lambda:

Source

Given that Lambda is a serverless service, the customer is responsible for a smaller amount of security. Why CTOs and CISOs love Lambda is because they do not need to manage the security with respect to the hardware, operating system, and networking infrastructure. Many companies spend millions securing, hardening, and configuring those 3 items alone. If you have worked at a large bank or secure/regulated industry like healthcare you know that to be true. In this model the customer is responsible for the actual code, resource configuration, and the identity and access management. Most important thing is to know how to secure those three customer responsibilities, but having a knowledge of how AWS keeps Lambda secure on the backend is good to know, as the number of people who know both is few.