AWS IoT Greengrass
Edge runtime on customer hardware that runs components locally, buffers data and syncs with AWS IoT when connected.
- Provider
- aws
- Kind
- Edge appliance
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| cloudManaged | boolean | — | no | true | ▸ true |
| connectivity | enum | connected | intermittent | disconnected | no | — | ▸ intermittent |
| formFactor | enum | rack | ruggedized | virtual | no | — | inherited |
| localDataEncryptedAtRest | boolean | — | no | false | inherited |
| localMqttBroker | boolean | — | no | false | inherited |
| localStorageGib | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| offlineMode | boolean | — | no | — | ▸ true |
| otaUpdates | boolean | — | no | true | inherited |
| streamManager | boolean | — | no | false | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "iot-greengrass", component: "aws-iot-greengrass" }Cloud Storage Gatewayalibaba-cloud-storage-gatewaySmart Access Gatewayalibaba-smart-access-gatewayAWS Backup gatewayaws-backup-gatewayAmazon EKS Anywhereaws-eks-anywhereAmazon FSx File Gatewayaws-fsx-file-gatewayAWS IoT Greengrass Version 1aws-iot-greengrass-v1AWS Outposts rackaws-outpostsAWS Storage Gatewayaws-storage-gatewayAKS Edge Essentialsazure-aks-edge-essentialsAzure Data Box Gatewayazure-data-box-gatewayAzure IoT Edgeazure-iot-edgeAzure IoT Operationsazure-iot-operationsAzure Localazure-localOn-premises data gatewayazure-on-premises-data-gatewayAzure Operator Nexusazure-operator-nexusAzure Stack Edgeazure-stack-edgeAzure Stack Hubazure-stack-hubCloudflare One Appliancecloudflare-one-appliancebalenabalenaGeneric edge applianceedge-applianceKubeEdgekubeedgeOpenYurtopenyurtGoogle Distributed Cloud air-gappedgoogle-distributed-cloud-air-gappedGoogle Distributed Cloud connectedgoogle-distributed-cloud-connectedGateway Applianceibm-gateway-applianceOracle Compute Cloud@Customeroci-compute-cloud-at-customerOracle Compute Cloud@Customer Isolatedoci-compute-cloud-at-customer-isolatedOracle Private Cloud Applianceoci-private-cloud-applianceOracle Roving Edge Infrastructureoci-roving-edgeOracle Roving Edge Classicoci-roving-edge-classic
# yaml-language-server: $schema=../../schema/component.schema.json # AWS IoT Greengrass V2 core device: the Greengrass Core software running on the customer's own # Linux or Windows edge hardware, deployed and updated from the cloud service. "How AWS IoT # Greengrass works" describes local component execution, local pub/sub and OTA updates from the # cloud; "Manage data streams on Greengrass core devices" states stream manager works with # intermittent or limited connectivity and does not encrypt stream data at rest on the device. schemaVersion: "1" type: "component" id: "aws-iot-greengrass" kind: "edge-appliance" provider: "aws" docs: "https://docs.aws.amazon.com/greengrass/v2/developerguide/manage-data-streams.html" defaults: connectivity: "intermittent" offlineMode: true cloudManaged: true managed: false properties: streamManager: type: "boolean" default: false localMqttBroker: type: "boolean" default: false localDataEncryptedAtRest: type: "boolean" default: false otaUpdates: type: "boolean" default: true