IoT Core OTA Job FAILED retry techniques

0

Hi there IoT people,

I am looking into the best practice approach to retrying an OTA update to failed devices.

Scenario:

"Let's say we ran an OTA update for 1000 devices, and 42 of them FAILED for some reason. We corrected the "reason" and now need to rerun the job for 42 devices only.

So, I looked thru the API's and I got as far as

Attach a lambda to a IoT Rule that filters for Completed events, as per

The next logical step is call ListJobExecutionsForJob, passing in the job Id, filtering for FAILED jobs only.

But I can't see a way to marry up the Execution to a Thing, because you need the thing name to call DescribeJobExecution.

Do you need to use Fleet Indexing, or is there a better way to programmatically get the list of failed Things for an OTA Job, so we can alert / report / build retry tooling?

Thanks!

AWS
已提問 4 年前檢視次數 492 次
1 個回答
0
已接受的答案

ListJobExecutionsForJob returns the ThingArn which is arn:aws:iot:<region><account-id>:thing/<thing-name>. You can extract the ThingName from that.

已回答 4 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南