- Newest
- Most votes
- Most comments
Hello,
Yes, you are correct. Due to the transitive nature of the Internet network, there could be chances that, at times, some of the message send to HTTP endpoints get dropped. Although this is very rare, It could occur.
In this case, as shared in the error message, IoT Rule service was unable to send the message to API Gateway as the request got timeout even after 2 retries. Since the request hasn't reached API Gateway, you will not be able to see anything on API gateway metrics or logs.
On such cases, the recommended approach is to use the IoT Rules error action [1] to capture such messages and retry with exponential backoff [2]. Since such errors are transitive, the messages would get through when retried after some time.
[1] https://docs.aws.amazon.com/iot/latest/developerguide/rule-error-handling.html [2] https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/
hello thank your for your answer.
I set up a SNS notification to start. But in your opinion which will be the best way to re-execute those actions ? I republish to another topic with the same action, or send to a queue or S3 ?
Thank you and have a nice day.
Relevant content
- asked 8 months ago
- asked a year ago
- asked 8 days ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 7 months ago
Additional links: