- Greengrass components depend on some system offerings, such as
java. Components which you create may have more dependencies including packages installed from apt/yum for example.
- When Greengrass starts up (or restarts), all components go through the
installphase again before running. If a component is written properly, then it will install all that it needs to work properly at this time.
- As long as the Greengrass root directory remains intact, Greengrass should be able to restart and operate normally.
If you're having a specific issue, please do comment with more details. But if you're just asking how things work in general, then I hope this helps.
System fullimage OTA upgrade and greengrass componennt dependenciesAccepted Answerasked 2 months ago
Greengrass core IoT OTA on Raspberry PIasked a month ago
How do I upgrade Greengrass Nucleus?Accepted Answerasked a month ago
Running greengrass-cli from a greengrass component; what's going on here?asked 7 months ago
System Call Failureasked a year ago
Greengrass v2 running as non root userasked 2 years ago
Greengrass install between partition based upgradesasked 6 months ago
Greengrass V2 read-only/read-write directories settingsAccepted Answerasked 2 years ago
Testing Greengrass Components Before Deployment with IPCasked 7 months ago
Greengrass Install Script Re-installs pip3 components every timeasked a year ago