IoT Building Blocks From Edge Devices to Analytics in the Cloud

© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Building Blocks for Smart Things
Madhusudan Shekar
@madhushekar23

© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved
What to expect from the session
1. Overview of AWS IoT
2. Use IoT rules engine to process data and move
data to AWS services
3. Building blocks of AWS IoT
4. Let’s see this working!

AWS IoT

Security is Priority #0
Connecting things securely
Protocols, Certificates and Security Policies

Securely connecting devices
• AWS IoT generated certificates
• Use your own certificate with Just In Time Registration
• Each device must have it’s own certificate
• Things/Devices must be in the registry
• Security policies are defined and attached

Protocol Support
• MQTT (Preferred)
• HTTPS
• Web Sockets (MQTT over WS over HTTPS)

Available AWS IoT Device SDKs
• C & C++
• iOS (Swift)
• Android
• Node.js
• Python
• Java

What does AWS IoT data look like?
PUBLISH turbines/ev-gen/123 (qos: 0)
{
"timestamp": "2016-11-29T10:00:00",
"temperature": 125,
"humidity": 95,
”rotor-freq": 6455,
“output”: 480,
“output-freq”: 60
}

First steps with AWS IoT
=+

And then…

© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved
AWS IoT IoT
shadow
Amazon
Cognito
MQTT over WebSockets
AWS
LambdaAlexa
Amazon
S3

Demo URL:
bit.ly/virtbulb

Lifecycle Events
Hello device, are you there?

Lifecycle events
1. Publishes a message when a client connects or
disconnects
2. $aws/events/presence/connected/<clientId>
3. $aws/events/presence/disconnected/<clientid>
{
”clientId": ”a1sb2568s0d08s08d0sdkasldkfei",
”timestamp": 1460065233478,
”eventType": “disconnected”,
”clientInitiatedDisconnect": true,
”sessionIdentifier": “000000-000-0000-0000-0000000000”,
”principalIdentifier": “000000/ABCDEFGHIJKLM:user/user-id”,
}

Device Shadows
Offline operations, command and control

AWS IoT Device Shadow

Publish on/off to the sprinkler
Device
Gateway
Sprinkler
Control logic
SUBSCRIBE
pune/sprinkler-456

Publish on/off to the sprinkler?
Device
Gateway
Sprinkler
Control logic
PUBLISH
pune/sprinkler-456
{ "water": "on" }

Direct publishing: why not?
Sprinkler
Control
logic
on
Device
Gateway
off
on
off

AWS IoT Shadow
{
"state" : {
“desired" : {
"lights": { "color": "RED" },
"engine" : "ON"
},
"reported" : {
"lights" : { "color": "GREEN" },
"engine" : "ON"
},
"delta" : {
"lights" : { "color": "RED" }
} },
"version" : 10
}
Thing
Report its current state to one or multiple shadows
Retrieve its desired state from shadow
Mobile App
Set the desired state of a device
Get the last reported state of the device
Delete the shadow
Shadow
Shadow reports delta, desired and reported
states along with metadata and version

Shadow topics – request
• /update
• /get
• /delete

Shadow topics – response
• /update/accepted
• /get/accepted
• /delete/accepted
• /update/rejected
• /get/rejected
• /delete/rejected

IoT rules engine

Rules engine

Rules engine: Extracting value from messages
• Filter messages with certain criteria
• Transform the payload of messages
• React based on messages
• Move messages to other topics
• Move messages to other systems
• Predict changes based on trends

What is a rule?
• ruleName: human-readable name
• description: human-readable description
• ruleDisabled: true/false
• sql: e.g. SELECT * FROM ‘pm/topic’
• actions:
• action 1:
• action 2:

Rules engine: Filter and transform
• SQL
• SELECT * FROM topic WHERE condition
• SELECT status.space_id AS room_id FROM
'iot/tempSensors/#' WHERE temp > 50
• Functions (in SELECT or WHERE)
• String manipulation (regex support)
• Mathematical operations
• Context-based helper functions
• Crypto support
• UUID, timestamp, rand, etc.

Rules engine: React (and move)
"rule": {
"ruleName": "republishPredictions”,
"ruleDisabled": false,
"sql": "SELECT no AS id, cycle AS c_number FROM 'pm/topic' WHERE failure = 1",
"description": "Republish ids of engines that are predicted to fail within 30 cycles",
"actions": [
{
"republish": {
"topic": "pm/failures",
"roleArn": "arn:aws:iam::012345678901:role/iot-actions-role”
}
}
],
}

Rules engine: Move messages to other systems
• Filter messages with certain criteria
• Transform the payload of messages
• React based on messages
• Move messages to other topics
• Move messages to other systems
• Predict changes based on trends

Rules engine: Move messages to other systems
Invoke a Lambda function
Put object in an S3 bucket
Insert, update a
DynamoDB table
Publish to an SNS topic
or endpoint
Publish to a Amazon Kinesis
stream
Publish to Firehose
Republish to AWS IoT
Publish to Amazon ES
Capture a CloudWatch
metric or change an alarm
Write to an SQS queue

Rules engine features
• JSON collections
• get(array, int) – get item at index of array
• get(string, int) – get character at position of string
• get(object, key) – get value of key
• SUB SELECT from collections
• SELECT (SELECT v FROM e WHERE n = 'temperature') as
temperature FROM 'topic'

Rules engine: Integrating data storage
Put object in an S3 bucket
Insert, update a
DynamoDB table
Publish to Firehose
Publish to Amazon ES
Publish to a Amazon Kinesis
stream

Connected Car

IoT Building Blocks From Edge Devices to Analytics in the Cloud

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to IoT Building Blocks From Edge Devices to Analytics in the Cloud

Similar to IoT Building Blocks From Edge Devices to Analytics in the Cloud (20)

More from Amazon Web Services

More from Amazon Web Services (20)

IoT Building Blocks From Edge Devices to Analytics in the Cloud