AWS IoT Greengrass

AWS IoT Greengrass is an edge runtime and cloud service that extends selected AWS functionality to on-premises and edge devices. It operates by running a Greengrass Core runtime on devices to execute components and AWS Lambda functions locally while synchronizing state and deployments with the cloud control plane. Greengrass typically fits between physical sensors/actuators and AWS cloud services to enable local compute, messaging, and intermittent-cloud workflows.

🗂 Resource Category

Internet of Things • Compute

🧠 Exam Memory Hook

Think: "Local edge compute + IoT connectivity + cloud sync = AWS IoT Greengrass"

📖 Ownership

Classification: Shared Responsibility Service

AWS responsibilities: AWS operates and patches the cloud control plane, management APIs, component repositories, and the AWS infrastructure that hosts these services, and provides integration points with services such as AWS IoT Core, Amazon S3, and AWS Lambda. AWS is responsible for the security and maintenance of the managed cloud platform, network infrastructure, and service endpoints. AWS publishes Greengrass runtime and component updates that customers can deploy, and protects the underlying physical servers and hypervisor in AWS-managed infrastructure.

Customer responsibilities: The customer installs, configures, and operates the Greengrass Core runtime on their edge devices, manages device identities and certificates, deploys and updates components and Lambda functions to devices, secures device operating systems and applications, and monitors device health and logs. The customer is responsible for network configuration, firewall settings, local resource access, lifecycle of device software, and any automation that applies component updates to fleets of devices. Operational tasks such as incident response on devices, provisioning hardware, and applying runtime or OS updates on devices are customer responsibilities.

Patching responsibilities: AWS patches and maintains the cloud-hosted control plane, service APIs, and AWS-managed infrastructure. Customers patch and maintain the device operating system, any hypervisor if used, the Greengrass Core runtime binaries installed on devices (including applying published Greengrass updates), installed runtimes, libraries, dependencies, and customer-deployed applications and components. If customers use virtualized or managed device hardware from a third party, patching responsibilities for that layer depend on the provider; otherwise device patching remains the customer's responsibility.

🏗 Typical Architecture

💡 Top 5 Features

Local execution of AWS Lambda functions and Greengrass components on edge devices to run compute close to data sources.
Local publish/subscribe messaging and inter-process communication between components using a lightweight local IPC model.
Component deployment and lifecycle management from the cloud control plane to device fleets, including component recipes and versions.
Secure device identity and mutual TLS authentication integrated with AWS IoT for authenticated device connections and authorization.
Support for intermittent connectivity by allowing local operation when cloud connectivity is limited and synchronizing data and state when available.

✅ Top 5 Use Cases

Performing local data pre-processing and filtering on devices to reduce upstream bandwidth and cloud ingestion costs.
Running real-time control or actuation logic with lower latency by executing functions locally on edge devices.
Deploying and updating edge software components and device logic centrally while maintaining device-local execution.
Executing machine learning inference at the edge to avoid sending raw sensor data to the cloud when latency or privacy requirements demand local processing.
Enabling devices to continue operating during intermittent cloud connectivity and synchronizing state or events to the cloud when connectivity returns.

🏗 Architecture Placement

AWS IoT Greengrass runs as a runtime on edge devices (the Greengrass Core) and connects to AWS IoT Core and other AWS services in the cloud; local sensors and actuators send data to the Greengrass Core, which executes components or Lambda functions and forwards selected data to cloud services. Management and deployments are performed from the AWS account-level control plane using AWS IoT and Greengrass APIs. Placement is device- and deployment-model dependent and typically involves device-level software communicating with regional AWS service endpoints.

🎯 Commonly Used With

- AWS IoT Core
- AWS Lambda
- Amazon S3
- Amazon CloudWatch
- AWS IoT Device Management

🌍 5 Real-World Examples

A manufacturing plant runs Greengrass on on-site gateways to perform real-time anomaly detection on machine sensor data and send only relevant events to the cloud for engineering analysis, reducing upstream data volume.
A healthcare remote-monitoring device executes local signal processing and alerts via Greengrass to meet low-latency response requirements while synchronizing patient telemetry to cloud records when connectivity is available.
A retail store uses Greengrass on in-store edge servers to run personalization logic and local caching for point-of-sale systems, enabling faster responses and continued operation during WAN interruptions.
A logistics provider runs asset-tracking gateways with Greengrass to aggregate and transform telemetry from multiple trackers at the edge, forwarding consolidated data to cloud services for route analytics.
An energy utility deploys Greengrass on field gateways to run local control loops and telemetry aggregation for grid sensors, allowing local decision-making and batch uploads to cloud storage for archival and analysis.

🎓 AWS Exam Clues

Requirement for low-latency local processing and offline operation often indicates AWS IoT Greengrass over cloud-only IoT solutions.
If the architecture requires running AWS Lambda or managed components on edge hardware, Greengrass is a candidate.
Designs that require central deployment of edge software and versioned component recipes commonly use Greengrass component management.
High operational responsibility for device OS and runtime patching differentiates Greengrass from fully managed serverless cloud services.
When intermittent connectivity is expected and local state persistence or queued synchronization is needed, Greengrass is applicable.

📝 Quick Revision

AWS IoT Greengrass provides an edge runtime for running Lambda functions and components on devices with cloud-managed deployments. Use it when local compute, low latency, or intermittent connectivity are required, and plan for device-level security, monitoring, and patching responsibilities.

🏷 Keywords

Greengrass Core • Greengrass components • local Lambda • IPC pub/sub • device identity • mutual TLS • offline sync • component recipe • fleet deployments • edge inference • AWS IoT Core • device provisioning