Learn how the technology behind AWS Greengrass works and how it fits into your IoT strategy. Let us guide you through all the technical aspects and requirements for getting AWS Greengrass setup and provide details on how to incorporate other key services such as AWS IoT, AWS Lambda, and Amazon API Gateway. The tech talk will walk through our LoRa Nano Gateway demo with AWS IoT and AWS Greengrass to see these services in action.

1. |Webinars© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Craig Williams, Partner SA & IoT Specialist
AWS Greengrass Technical Deep Dive

2. |Webinars
What to except from this session
• Quick re-cap of AWS IoT
• Why Greengrass?
• AWS Greengrass deep dive
• Short demo showing a working Greengrass group

3. |Webinars
AWS IoT Quick Re-cap

4. |Webinars
AWS IoT is a fully managed cloud platform that lets connected devices easily and
securely interact with cloud applications and other devices.
Extract and Filter data
from your devices and
take action with custom
Rules
Securely connect and
manage any physical
device across multiple
networks and protocols
Create Web and
Mobile Applications
that Interact with
Devices reliably at any
time

5. |Webinars
AWS IoT

6. |Webinars
AWS Greengrass Deep Dive

7. |Webinars
Why Greengrass?
Law of physics Law of economics Law of the land

8. |Webinars
Local
Lambda
Local
Device Shadows
Local
Security
Greengrass
is…
AWS
Local
Broker

9. |Webinars
NOT hardware—you bring your own
Greengrass
is…
AWS

10. |Webinars
Greengrass Core (GGC)
The runtime responsible for
Lambda execution, messaging,
device shadows, security, and for
interacting directly with the cloud

11. |Webinars
Greengrass Core (GGC)
• Min Single-Core 1GHz
• Min 128MB RAM
• x86 and ARM
• Linux (Ubuntu or Amazon)

12. |Webinars
Greengrass Core (GGC)
The sky is the limit.
GGC takes advantage of your
device’s compute, memory,
storage, and peripherals

13. |Webinars
IoT Device SDK
Any device that uses the IoT
Device SDK can be configured to
interact with Greengrass Core via
the local network
AWS IoT Device SDK supports C,
C++, Python, JavaScript

14. |Webinars
Devices work together locally
A Greengrass Group is
a set of Cores and other
devices configured to
communicate with one
another

15. |Webinars
Devices work together with the cloud
Greengrass works with
AWS IoT to maintain
long-lived connections
and process data via
the rules engine
Your Lambda functions
can also interact directly
with other AWS services

16. |Webinars
Local Lambda
Lambdas are event-driven
compute functions
With Greengrass you can write
Lambda functions in the cloud
and deploy them locally

17. |Webinars
Local Lambda
Greengrass runs Lambdas
written in Python 2.7
Invoke Lambda functions with
messaging and shadow updates

18. |Webinars
Local Lambda – What you can do
Command and control
Offline operation
Data filtering & aggregation
Iterative learning

19. |Webinars
Shadows
JSON documents that represent
state of your devices and Lambdas
Define them however is logical to
you—a car, an engine, a fleet
Sync to the cloud or
keep them local

20. |Webinars
Shadows – What you can do
Device state (current and desired)
Granular device state (only
synched to the cloud for debug)
Dynamic configuration (e.g,.
numeric factors of an ML model)

21. |Webinars
Messaging
Local MQTT Pub/Sub messaging
Define subscriptions between
publishers and subscribers
Apply MQTT topic filters

22. |Webinars
Security
Mutual auth, both locally
and also with the cloud
Certificate on your
devices can be
associated to SigV4
credentials in the cloud
You can directly call any
AWS service from
Greengrass

23. |Webinars
Security
The local GGC has it’s
own root certificate.
Each device certificate is
signed by the GGC’s root
certificate.
Greengrass core now
uses the local CA and
device certificate for
authentication.

24. |Webinars
Broker Specifics
Publisher
Connect to
GGC
• Cert verified
locally
Publish to
topic
Route
Table
• Match targets
• Reject by
default
Lambda or
Subscriber
Subscriber
Connect to
GGC
• Cert verified
locally
Subscribe
to topics
Route
Table
• Match targets
• Reject by
default
Receive
messages
Lambda
Receives
message
Compute
Publish to
topic
Route
Table
• Match targets
• Reject by
default
Lambda or
Subscriber

25. |Webinars
Detailed Requirements
• Linux – Kernel 4.4 with OverlayFS enabled (we test
on 4.4 but 3.18+ with OverlayFS is an option)
• x86_64, ARMv61, AArch64

26. |Webinars
Use Case - example
Gas Turbine Filter Maintenance
• Each turbine consists of multiple devices/sensors
• Each turbine has a single Greengrass core
• Lambda functions have enough logic to perform edge machine learning
• Models and Lambda changes can be centrally updated
• Lambda filters data and using it’s edge ML can determine when to request
maintenance/replacement of filters
• Only required data is sent up to AWS IoT once an hour
Lambdas
Rules
Shadowturbine
AWS
IoT

27. |Webinars
FAQ
What about shadow sizes?
• Shadows can be synced to the cloud and so the limit matches the cloud.
Can GGC’s communicate with each other?
• Not natively, you have to create a proxy using a connected “device” that will relay
between two cores
Can we use wildcards in the route table?
• No, explicit rules have to exist for all targets and sources
Can we subscribe to cloud topics?
• Yes, the source is “cloud” and you specify a local target
Can we compile for other architectures?
• No, please to your account team or partner team for support

28. |Webinars
Greengrass pricing
Active
Cores Price
3 Free for 1 year
3–10,000
$0.16/month
$1.49/year
10,000+ Call us

29. |Webinars
Demo

30. |Webinars
Demo Architecture
AWS
IoT
Lambda
API Gateway
AWS
IoT SDK
Gateway
LoRa Traffic
TCP Traffic
Data re-mapped,
re-published
MQTT Traffic
Lambda
Lambda

31. |Webinars