Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Setting up the edge device
Then, the root file system has to be configured according to the requirements described [https://docs.aws.amazon.com/en_us/greengrass/latest/developerguide/setup-filter.other.html here].
AWS documentation was a little bit confusing about the Node.JS and Java requirements. Both were installed, just in case. With regard to Java, OpenJDK 1.8.0 was installed.
To enable IP routing, the default gateway was setup like this:
<pre class="board-terminal">
root@sbcspg:~# route add default gw 192.168.0.254 eth0
</pre>
To verify that the device's configuration is setup properly, it is recommended to use the dependency checker script provided by AWS itself. The following image shows the output the checker executed on SBCSPG after completing the configuration.
[[File:GGC-checker.png|thumb|center|600px|Output of the GGC dependencies checker]]
As shown, only one check is highlighted. It refers to the kernel version. To run GGC 1.9.2, it is recommended a 4.4 kernel version or later. At the time of this writing, a newer kernel was not available for SBCSPG. To work around this issue, the [https://docs.aws.amazon.com/greengrass/latest/developerguide/lambda-group-config.html#lambda-containerization-groupsettings default Lamba functions containerization] was disabled.
==Configuring AWS Greengrass Core on cloud side==