1 Answer
- Newest
- Most votes
- Most comments
1
Hi. You can un-deploy a component in the same way as you deploy one. Revise the last deployment, remove the component, then deploy.
Uninstalling an exe file is trickier because Greengrass components don't have an Uninstall lifecycle. Add your voice here if you would like this feature: https://github.com/aws-greengrass/aws-greengrass-nucleus/issues/814. So you probably would need to manage the uninstall from the run state. In general though, you should be cautious about performing system wide changes from a component. Systems Manager might be a better choice.
Relevant content
- Accepted Answerasked 2 years ago
- asked 3 years ago
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 days ago
I tried to install Systems Manager components on my core device but the deployment fails with below error. Error COMPONENT_VERSION_REQUIREMENTS_NOT_MET: FAILED_NO_STATE_CHANGE: An error occurred while negotiating component version with cloud. The version of component requested does not claim platform compatibility. Check whether the platform constraints conflict and that the component platform mentioned in the recipe matches the platform constraints. If the platform constraints conflict, revise deployments to resolve the conflict. Component aws.greengrass.SystemsManagerAgent claimed platform: os windows, architecture amd64. Error code hierarchy • DEPLOYMENT_FAILURE • NO_AVAILABLE_COMPONENT_VERSION • COMPONENT_VERSION_REQUIREMENTS_NOT_MET
Greengrass Developer Guide, version 2 mentioned a note that "AWS IoT Greengrass doesn't currently support this feature on Windows core devices." But the AWS Systems Manager Documentation says Windows Server is supported. Have you ever used Systems Manager component on windows greengrass core devices?