Skip to content
Greengrass V2 Edge Walkthrough

Concepts

Greengrass V2
AWS IoT Greengrass V2 — edge runtime (Nucleus) plus cloud control plane for deployments, client devices, and local MQTT. runs software on an edge host and can connect local devices and cloud services. Terms below match how this walkthrough uses them.

Terms

Section titled “Terms”

On the NUC — edge

Client deviceUp to three ESP32-S3 zones: button, chip-temperature telemetry, RGBAssociateFlash zones
ComponentAuth, Moquette, Bridge, IPDetector, Cli, LogManager, GgEdgeLoop, ZoneAnomaly (ONNX)LoopInference
Nucleus litenot usedNot used — classic Nucleus on Ubuntu x86

In AWS — cloud

IoT CoreIdentities, discovery, bridged topics, IoT rules, cloud → edge commandsIdentitiesCommands
DynamoDBLatest state per zone: telemetry, actuator source, cloud ack, edge inferenceZone state
CloudWatchZone temperature metric + alarm → SNS; LogManager component logsRaise an alarmLogs
LambdaAlarm (via SNS) → command on gg-edge/cloud/command/<thing>Commands
SageMakerTrains per-zone anomaly models on the S3 lake → ONNX → Greengrass. Not Edge Manager (discontinued).Inference

Out of scope

Section titled “Out of scope”

Stream Manager, ESP32 firmware OTA, IoT Analytics, Device Defender, multi-core HA, Windows cores, Nucleus lite install, SageMaker Edge Manager, Docker components, console auto-provision as the only install path.

In scope after the local loop: Greengrass cloud deployments from S3, LogManager → CloudWatch Logs, IoT rules → S3 / DynamoDB / CloudWatch, SNS → Lambda → cloud-to-edge commands, and SageMaker-trained ONNX inference on the core. Start at Deploy from the cloud.

See also: Why Greengrass?.

Next: Why Greengrass?.