Become an AWS pro by learning to run serverless applications with AWS Lambda. Developed by AWS Solution Certified Architects. Get hands-on, no setup, no cleanup, no hassle.

aws_image.tar.gz

LANG

LC_ALL

aws_access_key_id

aws_secret_access_key

BUCKET_NAME

aws_region

dockerjob

dockerjob-copy

RunSamLogsTail

RunCfnLint

RunSamLocal

RunVersionCode

RunGradualDeployment

RunDeploymentAlert

RunChap6CustomisingResponses

RunChap6Processingrequestparameters

RunChap6GlobalSettings

RunChap6CreatingParameterisedCloudFormationStacks

RunChap7

RunChap8

RunChap9AvoidingCircularReferences

RunChap9ConditionalResources

RunChap10InvokingSystemUtilities

RunChap10PublishingToSAR

RunChap11UploadingFilestoS3

RunChap12LambdaUtilityFunctions

dockerjob-copy-ForceRelaunch

dockerjob-copy-copy-FR

RunSamLogsTail-copy

RunCfnLint-copy

RunSamLocal-copy

RunVersionCode-copy

RunGradualDeployment-copy

RunDeploymentAlert-copy

RunChap6CustomisingResponses-copy

RunChap6Processingrequestparameters-copy

RunChap6GlobalSettings-copy

RunChap6CreatingParameterisedCloudFormationStacks-copy

RunChap7-copy

RunChap8-copy

RunChap9AvoidingCircularReferences-copy

RunChap9ConditionalResources-copy

RunChap10InvokingSystemUtilities-copy

RunChap10PublishingToSAR-copy

RunChap11UploadingFilestoS3-copy

RunChap12LambdaUtilityFunctions-copy

RunSamLogsTail-copy1

RunVersionCode-copy1

RunGradualDeployment-copy1

RunDeploymentAlert-copy1

RunChap6CustomisingResponses-copy1

RunChap6Processingrequestparameters-copy1

RunChap6GlobalSettings-copy1

RunChap6CreatingParameterisedCloudFormationStacks-copy1

RunChap7-copy1

RunChap8-copy1

RunChap9AvoidingCircularReferences-copy1

RunChap9ConditionalResources-copy1

RunChap10InvokingSystemUtilities-copy1

RunChap10PublishingToSAR-copy1

RunChap11UploadingFilestoS3-copy1

RunChap12LambdaUtilityFunctions-copy1

In the world of modern development, serverless computing has become table stakes. Serverless computing has seen a major uptake with AWS Lambda having an increased adoption of 667% in 2018. Companies are making the switch to serverless for shorter time to market and decreased operational costs, but for you the advantage lies in the ability to offload the burden of managing infrastructure to serverless platforms, so you can focus on building even better apps.

In this course, you will learn how to run serverless applications using AWS Lambda. You’ll start with the basics such as creating a web service where you’ll learn the steps to deploy an AWS Serverless Application Model (SAM). You’ll then move on to more advanced topics such as handling HTTP Requests, using external storage, and managing sessions and user workflows. By the end of this course, you will be ready to work with AWS Lambda in a professional setting, and you’ll have a great, transferable skill that employers will love to see.

Running Serverless Applications with AWS Lambda

# Security requirements 
AWS does not trust a Lambda function to access a database or an S3 bucket just because they belong to the same account. You need to explicitly allow the use of each external resource from a Lambda function. To do that, you'll need to modify the IAM policy associated with a function.

Your function currently has two actions: 
1. displaying a form
2. processing the form

The form processing action will need access to an S3 bucket, but the form display action does not need any specific security access. When two different actions need different security levels, it's usually a good time to start thinking about breaking them into different Lambda functions.

With container-based applications, an API server process usually needs a superset of all the security permissions for all the contained actions. That makes setup and deployment easier, but it also means that a small security bug can easily turn into a disaster. If intruders break through a gatekeeper process, they can easily access all back-end resources. With Lambda functions, separating actions according to their security needs becomes very easy. Each function can have specific access to only the necessary resources. If a third-party dependency introduces a security issue in one of your API endpoints, the keys to the kingdom are still locked in a safe.

In [Chapter 6](https://www.educative.io/courses/running-serverless-applications-aws-lambda/processing-request-parameters), you created a new API endpoint to handle POST requests and just wired it up to the same function as the GET handler. Let's split the two endpoints into two functions so you can manage security better (see the figure below).

# `ShowFormFunction`
You can use this opportunity for some nice housekeeping. Let's do the following:

1. Rename the old Lambda function from `HelloWorld` to `ShowFormFunction`, so its purpose becomes clearer. 
2. Rename the function code directory on your disk from `hello-world` to something more meaningful, such as `user-form`, and update the `CodeUri` property of the function accordingly. 
3. Rename `app.js` inside the project code directory to something more meaningful, for example, `show-form.js`, and update the `Handler` property of the function accordingly.
4. Rename the first event mapping to something meaningful, for example,​ `ShowForm`.
5. Finally, instead of `/hello` as the API resource path, just use the root resource (`/`).



In this lesson, you will modify your application code to enable the access rights of Lambda functions. 

Lambda Access Rights

Getting Started

Setup Tools for Local Development

Creating a Web Service

Host a Serverless Application on AWS Lambda

Development and Troubleshooting

Core Features of AWS Lambda

Handling HTTP Requests

Using External Storage

Cheaper, Faster, Serverless

Handling Platform Events

Using Application Components

Managing Sessions and User Workflows

Designing Robust Applications

Deployment Options

Process Amazon SNS Notifications with AWS Lambda

Lambda Access Rights

Security requirements #