This whitepaper is for historical reference only. Some content might be outdated and some links might not be available.
2.3 Industrial IoT with AWS IoT Greengrass
Requirements addressed:
-
REQ1 (data residency)
-
REQ4 (availability and durability)
-
Customer-REQ1 (reliable connectivity)
AWS services –
AWS IoT Greengrass

Industrial IoT with AWS IoT Greengrass
AWS offers an IoT extension called
AWS IoT Greengrass
AWS IoT Greengrass can communicate with AWS IoT Core using public networks, such as the internet, as well as through Site-to-Site VPN or Direct Connect (refer to the dotted arrows in the preceding figure). Connectivity through Site-to-Site VPN or Direct Connect helps customers to not expose their local factory networks to the public internet, for safety and security reasons. By using VPC endpoints, customers can enable their devices to connect to AWS IoT Core using an endpoint that resolves to a private IP address within their VPC subnet. In addition, customers can restrict access to IoT Core to allow only connections over their VPC endpoint.
This lets you fulfill the following requirements:
-
REQ1 – The device can process (remove or anonymize personal data) and dump data to local storage on a device (local volumes or device resources) to provide a first data copy in the local country.
-
REQ4 – The ability to operate offline in situations when an online connection to AWS is not accessible, or intermittent. AWS IoT Greengrass buffers the data from devices for a period of time, and uploads the data when the connection is re-established.
-
Customer-REQ1 – Edge devices and IoT sensors are connected to local IoT AWS IoT Greengrass devices to decrease latency and improve reliability for intermittent connections.
Requirements REQ2 (data protection) and Customer-REQ1 (reliable connectivity) can be met through complimentary use of Architecture 1.1: Hybrid network connectivity from a data center to the AWS Cloud.