1 Answer
- Newest
- Most votes
- Most comments
1
Hello,
Unfortunately, IoT job for thing group deployment will not trigger again if that deployment revision for same thing name is executed before. To trigger an thing group deployment on a re-provisioned device, you will need to either 1) revise the deployment or 2) use a different thing name.
If you have a use case in which you need to re-provision devices at scale but unable to revise the deployment, we would love to hear more about it and see what we can do to improve the experience.
answered 2 years ago
Thank you for your answer.
As for a use case, think of an event organiser that would have to reset its devices for every event. I am aware that there would be ways around that.
Relevant content
- asked 3 years ago
- Accepted Answerasked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
Is the deployment associated with the fleet provisioning group using any variables or substitutions in the deployment document?
Yes indeed, fleet provisioning with the thing name using variable substitution.