Greengrass Device – Introduction

Regular Device: Sensor → Cloud → Process → Respond (high latency, always needs internet)

Greengrass Device: Sensor → Local Processing → Instant Response + Cloud Sync (low latency, works offline)

Local processing: You need to filter, aggregate, or transform data before sending it to the cloud.

Low latency response: Actions must happen in milliseconds (e.g., safety shutdowns, quality control).

Offline operation: Devices must continue working when internet connectivity is intermittent or unavailable.

Edge ML inference: Run machine learning models locally on sensor data without cloud roundtrips.

Protocol translation: Your sensors use legacy protocols (Modbus, BACnet, OPC-UA) and need local translation.

Gateway scenarios: One powerful device aggregates data from many constrained child devices.

Managed software updates: You need to deploy, update, and rollback application code remotely.

If your device has 512MB+ RAM and Java support → Choose Nucleus Classic

If your device is memory-constrained or runs embedded Linux → Choose Nucleus Lite

Greengrass core Device: Your physical Linux device running the Greengrass Nucleus runtime. It connects to /IOTCONNECT™ via MQTT and manages local components.

Component: A software module deployed to your device. Components run applications, collect telemetry, handle commands, and communicate with /IOTCONNECT™. Written in Python (or any language for Classic).

Recipe: A YAML or JSON file that describes a component — its name, version, dependencies, installation steps, and runtime configuration. Think of it as a Dockerfile for Greengrass.

Artifact: The actual application code (zip file) referenced by a recipe. Contains Python scripts, binaries, ML models, or any files needed by your component.

Package: A collection of components bundled together for deployment. In /IOTCONNECT™, a Package groups one or more components with a template.

Deployment: The act of pushing a Package (with selected components) to one or more target devices. Deployments are tracked with status: pending, successful, or failed.

IPC (Inter-Process Communication): The local pub / sub messaging system between components on the same device. Components publish telemetry on IPC topics that the /IOTCONNECT™ SDK picks up and sends to the cloud.

Template: Defines the data schema (attributes) and actions (commands) for your Greengrass devices. Components must send data matching the template attributes.

Industrial monitoring: Raspberry Pi gateway collects data from PLCs via Modbus, processes locally, sends aggregated metrics to cloud dashboards.

Smart agriculture: Field devices monitor soil moisture and trigger irrigation locally even without internet, syncing data when connectivity returns.

Predictive maintenance: Edge ML model detects vibration anomalies on factory equipment and triggers alerts in under 100ms.

Fleet management: Vehicle gateways running Greengrass aggregate GPS, fuel, and engine telemetry from multiple CAN bus sensors.

Retail / Building: Energy monitoring hubs process HVAC sensor data locally and only send hourly summaries to reduce bandwidth costs.

1. Create Template — Define what data the device will send (attributes) and what commands it can receive.

2. Create Device — Register the device in /IOTCONNECT™ with a Unique ID, select template, and choose Nucleus type.

3. Download Bundle — Download the connection kit (certificates + configuration) from the device list.

4. Install Nucleus — Transfer the bundle to your physical device and run the installer script.

5. Device connection — The Nucleus starts, authenticates with certificates, and the device shows as Connected in the portal.

6. Create Component — Write or download a component (application code + recipe) that generates telemetry.

7. Create Package — Bundle components together and associate with a template.

8. Deploy — Push the package to the device. The component starts running and sends telemetry.

9. Monitor — View live telemetry, check device health, execute commands, and review diagnostics.

10. Update — Deploy new component versions, add components, or rollback as needed.

Quick start guide — Get your first Greengrass device connected and sending telemetry in

approximately 15 minutes.

Device registration — Detailed walkthrough of creating templates and registering devices.

Package management — Learn how to create, deploy, and manage components.

SDK Development — Build custom components with the /IOTCONNECT™ Greengrass SDK.

Troubleshooting — Common issues and their solutions.