Deploying to AWS Lambda

Components

The deployment of code to AWS Lambda involves several major components as follows:

  • Functionthe custom code that processes events from an event source (see below) custom code in AWS Lambda is referred to as a Lambda function, which consists of code, associated dependencies, and configuration, see Lambda Function and Event Source
  • Layer – Lambda layers are a distribution mechanism for libraries, custom runtimes, and other function dependencies. Layers let you manage your in-development function code independently from the unchanging code and resources that it uses, see Lambda Layers
  • Event Sourcepublishes events that cause a Lambda function to be invoked, either by the event source in the "push" model, or by AWS Lambda in the "pull" model, see The Pull/Push Event Models

Workflow

The typical deployment workflow comprises one mandatory and two optional phases:

Create an AWS Lambda function

  1. upload the application source code (the 'Deployment Package') – see the Upload File(s) action of the Amazon S3 Object task

(Optional) Create an AWS Lambda Event Source Mapping (pull event model)

Illustration of the Lambda pull event model

(Optional) Add/Permit an AWS Lambda Event Source (push event model)

Illustration of the Lambda push event model

Illustration of the Lambda push event model

Alternative workflow via CloudFormation

A typical workflow based on CloudFormation might look as follows:

  1. upload the application source code (the 'Deployment Package') – see the Upload File(s) action of the Amazon S3 Object task

Frequently Asked Questions (FAQ)