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 routingThe following guides were useful to install some of the required packages:*https://tecadmin.net/install-latest-nodejs-npm-on-debian/*https://tecadmin.net/install-python-3-7-on-ubuntu-linuxmint/*https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-on-debian-9 A couple of file system setting must be tuned, too. They are hardlink and softlink protections. For more details about this, please refer to the default gateway was setup like thisfollowing links:<pre class="board*https://www.tecmint.com/protect-terminal">hard-and-symbolic-links-in-centos-rhel/root@sbcspg*https:~# route add default gw 192//access.168redhat.0com/documentation/en-US/Red_Hat_Enterprise_MRG/1.254 eth0<3/html/Realtime_Tuning_Guide/pre>sect-Realtime_Tuning_Guide-General_System_Tuning-Setting_persistent_tuning_parameters.html

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.

As shown, only one check is highlighted. It , which refers to the kernel version. To run GGC 1.9.2, it is recommended a 4.4 kernel version or later. At Although checker's report didn't warn about the time use of this writingcontainers, we verified that GGC didn't work with default Lambda functions containerization flags. Because a newer kernel was not available for SBCSPG. To at the time of this writing, 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.