Skip to content

Docker image for running AWS Greengrass on arm32v7 devices like WAGO PFC200 G2 or Wago Touch Panel

Notifications You must be signed in to change notification settings

WAGO/aws-iot-greengrass

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

29 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Statistics Docker Hub

DockerHub stars DockerHub pulls DockerHub azure-piplene build-status

Statistics Git Hub

GitHub issues GitHub stars

How to setup AWS IoT Greengrass on a Wago Device

Prerequisites for tutorial

Configure AWS IoT Greengrass on AWS IoT

https://docs.aws.amazon.com/greengrass/latest/developerguide/gg-config.html

Attention: Skip step 8b of the procedure because AWS IoT Greengrass core and its runtime dependencies are already set up in the docker image.


At the end of all steps you should have downloaded the security resources for the newly created Greengrasscore device.

  • <your_guid>-setup.tar.gz

This file will be needed in the later steps.

WAGO Device Configuration

Wago Device Login

Start SSH Client e.g. Putty

login as `root`
password `wago`

Check docker installation

docker info

Enable symlink and hardlink protection.

  • To enable the settings only for the current boot:
echo 1 > /proc/sys/fs/protected_hardlinks
echo 1 > /proc/sys/fs/protected_symlinks
  • To enable the settings to persist across restarts:
echo '# AWS Greengrass' >> /etc/sysctl.conf
echo 'fs.protected_hardlinks = 1' >> /etc/sysctl.conf
echo 'fs.protected_symlinks = 1' >> /etc/sysctl.conf

sysctl -p

Create a Greengrass working directory

You can create any working directory for Greengrass. (e.g.)

mkdir /home/greengrass
cd  /home/greengrass

Download the root CA certificate into the Greengrass working directory (for more information see the documentation https://docs.aws.amazon.com/iot/latest/developerguide/managing-device-certs.html).

  wget -O root.ca.pem https://www.amazontrust.com/repository/AmazonRootCA1.pem
or
  wget -O root.ca.pem https://www.symantec.com/content/en/us/enterprise/verisign/roots/VeriSign-Class%203-Public-Primary-Certification-Authority-G5.pem

Copy file "<your_guid>-setup.tar.gz" to greengrass working directory on your Wago device. (for this you can use WinSCP or any Ftp client)
Finally decompress file "<your_guid>-setup.tar.gz"

tar xvzf guid-setup.tar.gz

Afterwards, the working directory should contain following files.

working_folder

Running AWS IoT Greengrass Docker Container

docker run -it \
--init \
--name aws-iot-greengrass \
-v /home/greengrass/certs:/greengrass/certs \
-v /home/greengrass/config:/greengrass/config \
-p 8883:8883 \
wagoautomation/aws-iot-greengrass

The output should look like this example:

Setting up greengrass daemon
Validating hardlink/softlink protection
Waiting for up to 30s for Daemon to start

Greengrass successfully started with PID: 10

Persist Greengrass Runtime Logs outside the Greengrass Docker Container

You can run the AWS IoT Greengrass Docker container after bind-mounting the /greengrass/ggc/var/log directory to persist logs even after the container has exited or is removed.

docker run --rm --init -it --name aws-iot-greengrass \
--entrypoint /greengrass-entrypoint.sh \
-v /home/greengrass/certs:/greengrass/certs \
-v /home/greengrass/config:/greengrass/config \
-v /home/greengrass/log:/greengrass/ggc/var/log \
-p 8883:8883 \
wagoautomation/aws-iot-greengrass

Deploy Lambda Functions to the AWS IoT Greengrass Docker Container

You can deploy long-lived Lambda functions to the Greengrass Docker container.

Follow the steps in "Module 3 (Part 1): Lambda Functions on AWS IoT Greengrass" (https://docs.aws.amazon.com/greengrass/latest/developerguide/module3-I.html) to deploy a long-lived Hello-World Lambda function to the container.

Links

https://docs.aws.amazon.com/de_de/greengrass/latest/developerguide/run-gg-in-docker-container.html

About

Docker image for running AWS Greengrass on arm32v7 devices like WAGO PFC200 G2 or Wago Touch Panel

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published