Creating an IoT Cloud service for a connected product presents a huge challenge. Why? Because the tasks of serving millions, responding to events in near real-time, securing the solution from ambitious IoT hackers, AND generating a monthly bill that doesn't collapse the business model, resemble attempts to solve Rubik's Cube, but are far more difficult. Commercial IoT platforms are irrelevant because of the vendor-lock, so we must use basic building blocks to accomplish all this. This session will illustrate the architecture of an IoT service on top of the AWS Cloud.

1. Guy Vinograd, CEO
Device to IoT Solution
The Blueprint

2.  Million-scale users, 10000s devices
◦ AWS partner
 IoT clouds for device vendors
◦ Device vendors - focus on your core
◦ Customers - global $Bn companies to start-ups
About Me and Softimize

3. REST
The Components of an IoT Service
HTTP | MQTT | CoAP | XMPP
IoT
Backend Service
GW

4.  Cloud & Apps - today
 Gateway
◦ Mobile
◦ Dedicated
 RF
◦ BLE
◦ ZigBee
◦ Proprietary
 Sensors
IoT Best Practices – Call for Proposals

5.  No vendor lock
◦ Code ownership
◦ Cloud portability
 Cloud-native
◦ Minimal monthly bill (tenth!)
◦ Minimal devops
◦ Max security & compliance
◦ Max scalability & availability
IoT Cloud Best Practices - Basics

6. PaaS Platform In-house R&D
 Reasonable time-to-market
 Low investment
High OPEX
Vendor Lock
Long time-to-market
High investment
 Reasonable OPEX
 Exact Fit
Immediate Suspects for Building IoT Clouds
• >360 PaaS
• Unfit
database/API/deployment
• Dead (Parse.com)
• Not your IP
• >$10 / device / year
• Needs to master
• IoT
• SaaS
• Web / Mobile Apps
• Cloud
• Security & Privacy
• User & Product Analytics
• …

7. Security Multi Tenant DB
Data Streaming Vendor Services
Management
Enter TBBTM – A Great Open IoT Platform
Push notificationsDevice Interaction
Access Control – laas, SaaS
Vendor and cloud provider protection
Site management – Multi device
Licensing – per Tenant. Trial license
Bulk versioned FW updates
Complex event processing
Real-time, sub second latency
Users | Devices and hierarchies
Encryption, Tenant isolation
Audit
Analytics – Failures, Usage patterns
Prediction – Churn, Upsell
Discover & Config – w/o wifi | Real time streaming | FW update
Security – Encrypt, Auth | Reduce energy & bandwidth
On Premise
MQTT, HTTP
Built for Clouds
Multi Cloud
Abstraction Layers for managed services
NO DevOps-hungry open sources

8. Sensor Hub
K
i
n
e
s
i
s
Everything
DynamoDB
S3 or EFS
Session Files
Cloud Front
SQS
Agg
Trigger
Algo Agg
SQS
Agg
Ready
S3
Agg Out
Hub Logs
S3
Agg In
Auto Scaling
Auto Scaling
S3
DB
Backups
Redshift
Any SQL
BI Tool
Session Cache
RT Algo
AWS
IOT
MQTT
TBBTM Data Streaming – Zero DevOps

9. IoT Design Dilemmas

10.  Cloud – the ideal
◦ Protects IP
◦ Cheaper
◦ High availability/durability
◦ ..
 GW ("fog") – the reality
◦ Offline (rules, storage)
◦ True real time
◦ Data BW is large
#1 – Where is the Logic & Data?

11.  Temporal Stream Compression
#2 – How to Reduce Energy & Bandwidth?

12.  Protect
◦ Mutual device-cloud authentication
◦ x.509 certificates
◦ Encrypt sensitive data
◦ Key management
 Backup
 Traceability
 Voluntary compliance – ISO 27001
 AWS? Use HIPAA-Eligible, KMS, Cloud Trail
#3 – How to Secure the Solution?

13. Guy Vinograd
guy@softimize.co
Developing a Cloud-Native IoT Service?
Use