AWS has launched AWS Greengrass, a platform that extends the AWS Cloud onto your devices so they can act locally on the data they generate, while still taking advantage of the cloud. In this session we will talk about how Greengrass works and what you can do with it. You will also hear from early customers who will discuss their use cases for Greengrass and how it fits into their overall IoT strategy.
2. We can't overestimate the value of computers.
Yes, they are great for playing games and forwarding
funny emails. But real business is done on paper.
“
3. Most machine data never reaches the cloud
Medical equipment Industrial machinery Extreme environments
4. Why this problem isn’t going away
Law of physics Law of economics Law of the land
5. Three pillars of IoT
Things
Sense
& Act
Cloud
Storage
& Compute
Intelligence
Insights &
Logic → Action
7. AWS Greengrass
Cloud
AWS Greengrass extends AWS onto your devices, so they can act locally on
the data they generate, while still taking advantage of the cloud.
12. Greengrass Components
Greengrass is software, not
hardware (you bring your own)
2 Components that work together:
• Greengrass Core
• IoT Device SDK
13. AWS Greengrass Core (GGC)
The runtime responsible for
Lambda execution, messaging,
device shadows, security, and for
interacting directly with the cloud
14. AWS Greengrass Core (GGC)
• Min single-core 1 GHz
• Min 128 MB RAM
• x86 and ARM
• Linux (Ubuntu or Amazon)
• The sky is the limit
15. IoT device SDK
Any device that uses the IoT
device SDK can be configured to
interact with AWS Greengrass
core via the local network
Devices can be small or big
Starts with the IoT device SDK
for C++, more coming soon
16. Devices work together locally
An AWS Greengrass group
is a set of cores and other
devices configured to
communicate with one
another
17. Devices work together with the cloud
AWS 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
19. Local Lambda
Lambda functions are event-driven
compute functions
With AWS Greengrass you can
write Lambda functions in the
cloud and deploy them locally
20. Local Lambda
AWS Greengrass runs Lambda
functions written in Python 2.7
Invoke Lambda functions with
messaging and shadow updates
21. Local Lambda—What you can do
Command and control
Offline operation
Data filtering and aggregation
Iterative learning
22. Shadows
JSON documents that
represent state of your devices
and Lambda functions
Define them however it is logical to
you—a car, an engine, a fleet
Sync to the cloud or
keep them local
23. Shadows – What you can do
Device state (current and desired)
Granular device state (only
synched to the cloud for debug)
Lightweight configuration
24. Messaging
Local MQTT pub/sub messaging
Define subscriptions between
publishers and subscribers
Apply MQTT topic filters
25. 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 AWS Greengrass
28. GOAL TO
DEMONSTRATE
Mini-Fulfillment Center Demo
Actions that are local, interdependent, and coordinated
“Cloud-like” local architecture of decoupled
and generally stateless microservices
Model sorting of packages shipped between fulfillment centers
29. Local device logic
Local communication
Local Lambda
20/sec
20/sec
20/sec
Mini-Fulfillment Architecture
30. Local device logic
Local communication
Local Lambda
20/sec
20/sec
20/sec
Mini-Fulfillment Architecture
31. Local device logic
Local communication
Local Lambda
20/sec
20/sec
20/sec
Mini-Fulfillment Architecture
32. Local device logic
Local communication
Local Lambda
20/sec
20/sec
20/sec
Mini-Fulfillment Architecture
33. Greengrass Helped Mini-Fulfillment Demo by:
Local Lambdas and Shadows enable
resilient coordinated actions across hosts
High frequency sample rate supports rapid error detection
• Communication as fast as physical transport allows
Local MQTT router enables strongly
decoupled and yet secure communications
Lambdas enable “Octopus-like intelligence”
spread across the solution
35. TECHNICOLOR plays a key role in all phases of CONTENT
CREATION DISTRIBUTION CONSUMPTION
#1 IN HOME
GATEWAYS
#2 IN SETTOP
BOXES
500M DEVICES
SHIPPED
250 OPERATORS
GLOBALLY 80% CE VENDORS
USE OUR IP
40K PATENTS
#1 IN PRE & POST
PRODUCTION
70% OF HOLLYWOOD
BLOCKBUSTERS
150K VFX SHOT
ANNUALLY
36. New Technicolor PRODUCTS and SERVICES with Greengrass
10Gb Broadband GW
Extraordinarily powerful – Best Wi-Fi
Carrier-grade – Full service platform
Tri-band Wi-Fi Extender
Whole home coverage – Cool design
Intelligent diagnostics and roaming
Personal Assistant
Voice-activated user experience
App – Helpdesk optimization
37. PROBLEMS SOLUTIONS BENEFITS
LAMBDAS and CONTAINERS TTM, TCO, SecurityMONOLITHIC FIRMWARE
BENEFITS of Greengrass
EDGE COMPUTECLOUD HOSTING COSTS Cost, Privacy
CLOUD DEVELOPMENT MODELEMBEDDED SW SKILLS Dev Community
FLEXIBILITY to DECIDE WHEN,
WHERE and HOW to DEPLOY SERVICES
40. CONCLUSIONS
Clear BENEFITS ► Greengrass enables faster TTM, reduced TCO and
increased FLEXIBILITY and PRIVACY to the benefit
of Technicolor, service providers and consumers
OPPORTUNITY! ► By building bridges between CLOUD and EDGE,
we are creating opportunities for INNOVATION and
improved consumer EXPERIENCES in the home
New PRODUCTS ► As leading vendor in the connected home,
TECHNICOLOR is excited to introduce Greengrass
starting with these new PRODUCTS and SERVICES
44. Why Greengrass is important
Data processed
in the cloud
Data
processed
locally
Embedded
developer
Cloud
developer
Program devices with
modern languages,
deployment APIs, and
workflows
Cloud-based
development that adds
value to data that never
reach the cloud
Execute code locally
in response to data
45. How to get started today
Sign up for limited preview
Order AWS Snowball Edge
http://aws.amazon.com/Greengrass