Skip to content

Latest commit

 

History

History
 
 

aws-node-iot-event

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 

Serverless IoT Event

This example demonstrates how to setup a AWS IoT Rule to send events to a Lambda function.

Use-cases

  • Analytics for IoT events
  • Reacting on IoT events

Setup

In order to deploy the function simply run

serverless deploy

The expected result should be similar to:

Serverless: Packaging service...
Serverless: Uploading CloudFormation file to S3...
Serverless: Uploading service .zip file to S3 (363 B)...
Serverless: Updating Stack...
Serverless: Checking Stack update progress...
................
Serverless: Stack update finished...
Service Information
service: aws-node-iot-event
stage: dev
region: us-east-1
api keys:
  None
endpoints:
  None
functions:
  aws-node-iot-event-dev-log: arn:aws:lambda:us-east-1:377024778620:function:aws-node-iot-event-dev-log

Usage

In serverless.yml the log-function is configured to receive any event from the IoT Topic mybutton. We now can go to the IoT Console and visit the Tab Test.

There fill mybutton into the topic input field in the publish section. Replace existing example data with the following example and press the publish button.

{
  "message": "My first IoT event",
  "value": 2
}

To verify that our event was forwarded to our log-function run

serverless logs --function log

The expected result should be similar to:

START RequestId: 241921d10f-11e6-936c-a98ff4127599 Version: $LATEST
2002 18:16:04.768 (+01:00)	241921d10f-11e6-936c-a98ff4127599	{ message: 'My first IoT event', value: 2 }
END RequestId: 241921d10f-11e6-936c-a98ff4127599
REPORT RequestId: 241921d10f-11e6-936c-a98ff4127599	Duration: 23.53 ms	Billed Duration: 100 ms 	Memory Size: 1024 MB	Max Memory Used: 8 MB

In the output you can see the IoT event that has been triggered from the test console.