Bureaucrats, dave_user, Administrators
4,650
edits
Changes
no edit summary
Within the processing power limits of the edge device, moving such computations to the edge can be an effective way to optimize costs. When the Internet connection is intermittent or poor, it may even be mandatory to meet system's requirements. Generally speaking, when implementing an IoT system, balancing between cloud computing and edge computing is one of the most important issues the system architect has to address.
It should be stressed that this Technical Note is not a step-by-step guide to set up the edge device and the cloud platform to implement a Greengrass-based system. AWS documentation is rich and detailed in this regard. Rather, this document aims to underline some specific SBCSPG-related steps required to run GGC on this device successfully. The procedure is based on the [https://docs.aws.amazon.com/greengrass/latest/developerguide/gg-gs.html ''Getting Started with AWS IoT Greengrass'' guide], which is, therefore, a recommended reading.
The test was performed with:
==Setting up the edge device==
The first thing to do was to rebuild the Linux kernel after adding the missing options—if any—required options required by GGC, which are detailed [https://docs.aws.amazon.com/en_us/greengrass/latest/developerguide/what-is-gg.html#gg-platforms here].
Once the device was up and running with the fresh Linux kernel, to enable IP routing to the Internet, the default gateway was setup like this:
On the cloud, the log of the received messages should look looked like this:
[[File:AWS-GGC-hello-world.png|thumb|center|600px|Received messages on the cloud]]
