Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Setting up the edge device
</pre>
Then, the root file system has had 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 setup <code>cgroups</code>, [https://raw.githubusercontent.com/tianon/cgroupfs-mount/master/cgroupfs-mount this script] was used.
Finally, a couple of file system setting must had to be tuned, too. They are hardlink and softlink protections. For more details about thisthese settings, please refer to the following links:
*https://www.tecmint.com/protect-hard-and-symbolic-links-in-centos-rhel/
*https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/1.3/html/Realtime_Tuning_Guide/sect-Realtime_Tuning_Guide-General_System_Tuning-Setting_persistent_tuning_parameters.html
</pre>
To verify that the device is setup properly, it is recommended to use the dependency checker script provided by AWS itself. The following image shows the output of the checker executed on SBCSPG after completing the configuration.
As shown, only one check is highlighted, which refers to the kernel version. To run GGC 1.9.2, it is recommended a 4.4 kernel version or later. Although checker's report didn't warn about the use of containers, we verified that GGC didncouldn't work with default Lambda functions containerization flagson top of SBCSPG's 4.1.15 Linux kernel. Because a newer kernel was not available for SBCSPG 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.
In order to make the checker happy, two symbolic links were created as well: