- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
We now have documentation for manually setting up Greengrass. See: https://docs.aws.amazon.com/greengrass/v2/developerguide/manual-installation.html
Cheers,
Michael Dombrowski
Hi, we're doing exactly this right now. We generate the device certs ourselves, and I have a "deviceConfig.tmp" template file that our install scripts take the thing name and substitute that in the template and generate "deviceConfig.yaml". From there we can pass:
--config ./deviceConfig.yaml
in to the installer and it will use those values. We also have a provisioning template attached to our CA to provision the IoT thing. When Greengrass starts, it will (after two minutes) send the appropriate messages, and a GG Core device is automatically created.
Hope that helps!
Hi,
Many thanks for some advices. I will try to implement something similar on our end.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
One detail missing from that document is to know what other things happen when we run the command
sudo -E java -Droot="/greengrass/v2" -Dlog.store=FILE \ -jar ./GreengrassInstaller/lib/Greengrass.jar \ --init-config ./GreengrassInstaller/config.yaml \ --component-default-user ggc_user:ggc_group \ --setup-system-service true
I see that it installs
/etc/systemd/system/greengrass.service
- are there any other changes made outside the greengrass directory?