A starter module for an AWS Lambda that can handle S3 PUT notifications and Kinesis stream events.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.gitignore Initial commit. Apr 27, 2015
LICENSE Add MIT license. May 11, 2015
Makefile Initial commit. Apr 27, 2015
MyLambda.js Initial commit. Apr 27, 2015
README.md Readme. Apr 27, 2015
demo-invoke-kinesis-payload.json Initial commit. Apr 27, 2015
demo-invoke-s3-payload.json Initial commit. Apr 27, 2015
package.json Initial commit. Apr 27, 2015
test.js Initial commit. Apr 27, 2015


S3 / Kinesis Lambda Starter

A starter module for an AWS Lambda that can handle S3 PUT notifications and Kinesis stream events.

This module is intended to be copied and edited as your own Lambda function. The utilities within this repo are focused around creating and maintaining a single Lambda function.

Read the accompanying blog post here.


  • npm install


  • npm test


First, set your AWS_ACCOUNT_ID environment variable:

  • bash: export AWS_ACCOUNT_ID=123
  • fish: set -x AWS_ACCOUNT_ID 123


There are two specific permissions that you'll likely need.

  • User permission for iam:PassRole. This policy needs to be applied to the user who is creating the Lambda:
  "Version": "2012-10-17",
    "Statement": [
        "Sid": "Stmt1429124462000",
        "Effect": "Allow",
        "Action": [
        "Resource": [
  • Lambda execution role. You need to create a new role that the Lambda will run as. We assume that role is named lambda_basic_execution for the purposes of this project. That role must have (at least) this policy applied:
  "Version": "2012-10-17",
  "Statement": [
      "Effect": "Allow",
      "Action": [
      "Resource": "arn:aws:logs:*:*:*"

This policy allows the lambda_basic_execution role to manage CloudWatch logs for our Lambda's execution.


  • make upload

Connect an S3 bucket:

To connect an S3 bucket to the Lambda function, you must use the AWS UI.

Connect a Kinesis stream:

To connect a Kinesis stream to the Lambda function, run the following:

aws lambda add-event-source \
   --region <region> \
   --function-name <lambda-function-name> \
   --role arn:aws:iam::<account-number>:role/<role-name> \
   --event-source arn:aws:kinesis:<region>:<account-number>:stream/<kinesis-stream-name> \
   --batch-size 100 \
   --profile <cli-profile-name>

Note: cli-profile-name is whatever block you've named your credentials in ~/.aws/credentials. It is default by default.


We've defined some useful utilities in the Makefile which can make uploading, updating, and invoking this Lambda a little easier.

Note: We have hardcoded the region and function name into the Makefile for this module. You'll want to modify this if you plan to change the function name or use a region other than us-east-1.

  • make delete - will remove this Lambda from AWS.
  • make get - will retrieve the details of this function on AWS.
  • make invoke - will invoke this Lambda on AWS with the provided data file.
  • make list - will list all of the Lambda functions on this account for the given region.
  • make list-event-sources - will list event sources for this Lambda.
  • make update - will re-upload this Lambda package without overwriting the function's configuration details.
  • make upload - will upload this Lambda function for the first time.