Ao usar o AWS re:Post, você concorda com os AWS re:Post Termos de uso

Is there a way to install Greengrass deployment components to a recovered device?

0

In our AWS IoT Greengrass implementation, we have a Deployment targeting a Thing Group.

During the first time setup once our device has been registered in AWS IoT (as a Thing, and Core Device), the deployment is queued and completed as expected, installing all required GG components.

NOTE: We are using a static thing name based on our Hardware serial number, so this thing name cannot be modified or duplicated.

If for some reason we need to reflash our device (for example due to filesystem corruption, or a Linux BSP update that requires reflashing the SD Card), when doing the first-time setup again, on the same unit, we do not get the components installed because there is no Deployment job scheduled (and we understand that this is because the deployment completed and the Thing and Core Device already existed).

So, for now, we have 2 workarounds, the first is to delete the Thing and Core Device from the AWS IoT console before reflashing a device to prevent this situation, and the second is to Revise the Deployment.

The question is, is there a way to tell Greengrass that the device needs a "re-deploy" of the components or something like that?

This was not an issue before for us because we were using randomly generated thing name IDs, but now we are using static names this is an issue.

Your help will be much appreciated.

Thanks,

profile picture
feita há 2 anos436 visualizações
1 Resposta
0

Hi,

if your deployment is targeting the specific device, my advice is to revise the deployment.

if you are using a group as target for your deployment you can remove the thing from the group and add it to the group again - this forces a deployment only to this specific device.

Massimiliano

AWS
ESPECIALISTA
respondido há 2 anos
  • So there is no way to do this automatically? I have the same kind of issue. I don't want to do any manual work to achieve this. Can't I retain the last deployment etc?

Você não está conectado. Fazer login para postar uma resposta.

Uma boa resposta responde claramente à pergunta, dá feedback construtivo e incentiva o crescimento profissional de quem perguntou.

Diretrizes para responder a perguntas