- 최신
- 최다 투표
- 가장 많은 댓글
The "AWSManagedGreengrassV2Deployment" shadow is created when a thing deployment is created. This deployment shadow isn't created just because a core device is provisioned. The console flow will create a deployment for the customer to deploy dev tools.
With fleet provisioning, unless you use a pre-provisioning hook that creates a "thing" deployment, there is no shadow no thing deployment is created.
The "ERROR" is not a failure - Greengrass on the device is asking for the deployment shadow to see if there is a deployment it needs to process. When no deployment has been created, this will log as an error in IoT logs because it is asking for a shadow that doesn't exist. The device handles this as there is no deployment necessary.
Clarification update: The missing shadow does not cause any cloud or device impact with Greengrass. It is expected to see this log if you don't create a thing deployment. As Michael mentioned, thing group deployments do not update the shadow for each thing in the group.
관련 콘텐츠
- AWS 공식업데이트됨 8달 전
Thanks for the reply, that sounds plausible. However, I create a deployment for a ThingGroup via CDK. The deployment runs without problems, but the shadow is not created. I create the deployment before I create a coreDevice so that it automatically receives the deployment.
Do I have to create the shadow manually or could it be due to an error when creating the deployment?
Hi Marco, Group deployments do not use shadow. Whether or not the shadow exists does not matter.
The deployment shadow is created only when making a thing (not group) deployment. This will happen if you're installing using
--deploy-dev-tools true
.