- Newest
- Most votes
- Most comments
POTENTIAL ANSWER TO #1 & #3:
Next steps -- "manual provisioning" --> [1]
use the already existing "GreengrassInstaller" installed when the device was initially "provisioned"
-->
provide a fully configured ~/GreengrassInstaller/config.yaml (using data pulled from the "partial-config" file that was used in "fleet-provisioning"):
-->
run the installer with necessary args. [2]
-->
restart greengrass ==> sudo systemctl restart greengrass.service
[1] https://docs.aws.amazon.com/greengrass/v2/developerguide/manual-installation.html
[2] https://docs.aws.amazon.com/greengrass/v2/developerguide/manual-installation.html#run-greengrass-core-v2-installer-manual
POTENTIAL ANSWER TO #2: assists in the creation of aws iot resources when using the fleet-provisioning create-keys topics?
Although I have attempted to reinitilize the Greengrass installation using an updated config.yaml file (this file includes the updated informatin for file paths to certs, data-endoint, credential-endpoint, etc) for greengrass to work correctly as a fully configured device --- BUT I am still not seeing a "greengrass core" device being created at any point.
Should this have happened when the "thing" connected for the first using the "permanent" certificates produced from "fleet-provisioning"?
Edited by: awiggins on Oct 26, 2021 6:21 PM
Welp.... it helps to save the credentials that you are receiving back from Fleet Provisioning Topics into their respective .pem & private key file to be used when Greengrass starts back up --> smh
I do hope someone finds this helpful...
Relevant content
- asked 3 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 4 months ago
I am having the exact the same problem... I get an IoT thing registered but no the GGV2 Core Device, which I assume shall be created after the Fleet provision. How do I know provision went well? I have the thingCert.pem in "/greengrass/v2/" folder and the thing is created in IoT Core. I get these errors in "/greengrass/v2/logs/greengrass.log"