AWS Greengrass
AWS Greengrass
AWS IoT Greengrass API deploys AWS Lambda and ML models to edge devices (IoT gateways, industrial equipment) for local data processing.
One-click cloud-to-fleet deployment of code/models to thousands of edge devices
Edge devices need sufficient resources (typically ≥512MB RAM)
Install Greengrass Core software on edge devices; CreateDeployment to deploy Lambdas/components. MQTT topics for cloud-edge data exchange.
Uptime · 30-day window
GitHub activity
About this API
Greengrass solves "all-data-to-cloud doesn't work" scenarios — factory floors with 1000 sensors per second produce too much data for network bandwidth; mining/offshore oil rigs have unstable networks; autonomous vehicles need millisecond decisions without cloud roundtrips. Greengrass extends AWS programming model to the edge: write Lambda (or define containers/ML models) in the cloud, Greengrass deploys to edge devices. Devices sync state to cloud every 30s; ML inference runs locally in real-time via Lambda, results uploaded as needed. Greengrass v2 (2020) is a rebuild from v1, more K8s-style component model. Direct competitors: Azure IoT Edge, Google Cloud IoT Edge. Best fit for industrial IoT in manufacturing, energy, agriculture, transportation.
What you can build
- 1Factory edge gateway pre-processes sensor data locally
- 2Devices keep working offline (sync after cloud reconnects)
- 3ML model inference at the edge (image detection, anomaly recognition)
- 4Bulk device fleet management
Strengths & limitations
Strengths
- One-click cloud-to-fleet deployment of code/models to thousands of edge devices
- Supports Lambda, containers, ML models as workloads
- Disconnect tolerance (buffer data locally)
Limitations
- Edge devices need sufficient resources (typically ≥512MB RAM)
- IoT fleet ops is inherently complex (heterogeneous devices)
- Greengrass v2 rebuild is not fully v1-compatible
Example request
curl https://github.com/mermade/aws2openapi/<endpoint>Getting started
Install Greengrass Core software on edge devices; CreateDeployment to deploy Lambdas/components. MQTT topics for cloud-edge data exchange.
FAQ
Greengrass v1 vs. v2?+
New projects: v2 (component architecture, more flexible). v1 mainly for legacy users.
Minimum edge device requirements?+
Greengrass v2 nucleus needs ~100MB RAM minimum, but actual workloads (Lambda, ML model) need more.
Technical details
- Auth type
- unknown
- Pricing
- unknown
- Protocols
- REST, MQTT
- SDKs
- python, javascript, go, java
- Response time
- 13 ms
- Last health check
- 5/12/2026, 7:36:33 AM
More from Amazon Web Services
AWS IAM Access Analyzer API analyzes IAM resource policies for over-privileged access or external access — proactively surfaces security risks.
Amazon Chime SDK API embeds real-time audio/video calling and chat into apps (meetings, messaging, PSTN calls).
Amazon CloudFront is the AWS CDN and edge service — accelerates static and dynamic content delivery, a standard for web performance.
Amazon CloudSearch is AWS's managed search service (gradually superseded by OpenSearch Service).
CloudWatch Application Insights API auto-detects application problems — intelligently identifies anomalies (slow SQL queries, memory leaks), reducing manual alarm configuration.
AWS Cognito Identity Pools API issues temporary AWS credentials to frontend apps — identity federation, guest users, direct AWS resource access.
Amazon Cognito User Pools deliver managed user signup, login, password reset, and MFA for applications.
Amazon Connect Contact Lens API uses AI to analyze Amazon Connect calls in real time — sentiment, keywords, compliance detection, auto-summary.