Awesome

iron-lambda

Lambda functions support for IronWorker cloud

What is this?

Use the iron-lambda to locally dev and test your lambda functions in the exact same environment it will have when running remotely on the IronWorker cloud.

The Workflow

The general workflow is the following:

1. Create your lambda function (or use existing one). All dependencies must in the current directory or in sub-directories.
2. Create an input/payload example file (check this into source control as an example, default name is ./event.json)
3. Run your lambda function locally inside an Iron.io Stack container.
4. Debug/test until you get it working properly.
5. Once it works like you want it to, upload it to IronWorker. You should only have to do this once until you want to make changes.

Getting Started

1. You'll need Docker installed and running on your machine to use this. Run:

docker info

This should print information about your Docker installation. If it doesn't, you don't have Docker setup properly.

2. You'll want to install the new Iron cli tool as well (not totally necessary, but makes things a lot easier):

curl -sSL http://get.iron.io/cli | sh

Or if you'd prefer to download it yourself, you can grab the latest release from here: https://github.com/iron-io/ironcli/releases

3. Check that the Iron cli tool was installed properly:

iron --version

4. Install this npm package globally:

npm install iron-lambda -g

5. Create new directory for your function development and enter inside it

mkdir your-iron-lambda-func
cd your-iron-lambda-func

6. Setup iron lambda template

iron-lambda setup

The lambda function is placed in lambda.js, feel free to change it.

exports.handler = function(event, context) {
    console.log( "event", event );
    console.log( "env", process.env );
    context.done();
};

where event is the payload passed to lambda function

Command Line Interface

setup

Inits you working directory with template

iron-lambda setup

Template contains the following files:

• .env - stores runtime enviroment variables (e.g. credentials, roles, security tokens & etc)
• deploy.env - stores variables for docker image building process (e.g. you docker hub repository and image version)
• Dockerfile
• lambda.js - the lambda function module, must export handler
• package.json

run

Quick run locally

iron-lambda run

Runs the lambda function inside default iron/node docker container. The event data to run lambda on (the payload) should be placed to ./event.json.

run-in-docker

Run locally inside docker container

iron-lambda run-in-docker

Builds a docker container and runs the lambda function inside it. The event data to run lambda on (the payload) should be placed to ./event.json. Make sure you've specified a valid docker repository name in DOCKER_REPO_NAME variable of ./deploy.env file.

deploy

Deploy your lambda function

iron-lambda deploy

Builds a docker container, deploys it to docker hub and registers in IronWorker cloud. Make sure :

• you have logged to docker (see docker login command) and has your Iron.IO project credentials in ./iron.json. This file you can obtain on Getting Started page inside your IronWorker project (https://hud.iron.io/dashboard).
• you have specified a valid docker repository name in DOCKER_REPO_NAME variable of ./deploy.env file.

Examples

• Amazon Simple Notification Service

Notes

Windows Users

If you are using boot2docker on Windows, please note the following:

The Linux VM in the boot2docker VirtualBox maps the c/Users directory in the VM instance to the C:\Users folder in Windows. So be sure your source code for your worker is in a folder under C:\Users, then cd to that folder in the context of the VM (in Boot2Docker terminal) and run it from there.