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:
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!
Many thanks for some advices. I will try to implement something similar on our end.
We now have documentation for manually setting up Greengrass. See: https://docs.aws.amazon.com/greengrass/v2/developerguide/manual-installation.html
Greengrass, deploy component to specific directoryasked 4 months ago
[Greengrass][IDT] question for Greengrass v2 IDT testing error on component/mqtt tests on our AIOT deviceasked 5 months ago
Can Greengrass use a Lambda in the Core if needed?asked a year ago
Manual installation of GGC V2 Core deviceasked 2 years ago
Greengrass V2 read-only/read-write directories settingsAccepted Answerasked 2 years ago
Is deployment mandatory for Grreengrass V2 to work on GGC device?asked a year ago
IoT Rule on Greengrass Core Device Health Statusasked 4 months ago
Greengrass IPC to IoT Core in low/no connectivity regionsasked 7 months ago
Fleet Provisioning -- Greengrass Core installation Issueasked a year ago
How to retreive GreengrassV2 Core Device's AWS IoT Thing nameAccepted Answerasked 2 years ago