POTENTIAL ANSWER TO #1 & #3:
Next steps -- "manual provisioning" --> 
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. 
restart greengrass ==> sudo systemctl restart greengrass.service
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...
Fleet provisioning and lambda triggering topicsasked a year ago
Greengrass v2 fleet provisioning retry in case of lack of the Internet connection.Accepted Answerasked 8 months ago
How to automate the creation of Greengrass Core Device Shadow with fleet provisioning?asked a year ago
Greengrass v2 fleet provisioning in dockerAccepted Answerasked a year ago
Just in time provisioning for Greengrass v2 core devicesAccepted Answerasked a year ago
IoT core greengrass fleet provision device side effectiveConfig.yaml does not have updated thingNameasked 8 months ago
AWS IoT - Provisioning devices that don't have device certificates using fleet provisioningAccepted Answerasked 6 months ago
Fleet Provisioning -- Greengrass Core installation Issueasked a year ago
Connection Interruption Error during Fleet Provisioningasked a year ago
Fleet Provisioning of GGv2 devicesasked 2 years ago