- Newest
- Most votes
- Most comments
Hi Oide,
To deploy a public component you do not need to create your own copy of it, which is what you're doing. Simply add the public component name and version into the deployment request. https://docs.aws.amazon.com/greengrass/v2/developerguide/create-deployments.html
Thanks Kwonyul. Your repo is very helpful. I got it working to create a local shadow manager. I really appreciate your quick response!!
To get my IoT code syncing local shadows to IoT core, I needed to set permissions for the policy that greengrass v2 uses connect so that the shadow manager so that it can communicate with the IOT core.
I needed to add some extra permissions to GreengrassV2IoTThingPolicy. I did this manually in the console via Thing->Certificate->Policies->GreengrassV2IoTThingPolicy
{
"Effect": "Allow",
"Action": [
"iot:GetThingShadow",
"iot:UpdateThingShadow",
"iot:DeleteThingShadow"
],
"Resource": "*"
}
Is there any way to add these permission using CDK?
Also, lastly :), are there any updates on using wildcards for Named Shadow in Shadow Manager syncing as per this post? My particular use case needs this as I would like a physical IoT device to create multiple local named shadows "on the fly" that can be managed in IoT core. Having to update the "Configuration merge" on the shadow manager component each time is a big limitation.
Many thanks for all your help! Oide
answered 4 years ago
Relevant content
asked 4 years ago
