AWS iot documentation change
Summary
Updated warning about wildcard topic patterns in republish rules to recommend avoiding them to prevent duplicate processing and reduce costs, removing mention of infinite loops
Security assessment
The change emphasizes operational efficiency (duplicate processing and cost reduction) rather than explicitly addressing a security vulnerability. While infinite loops could theoretically cause resource exhaustion (a security concern), the updated text does not frame this as a security issue.
Diff
diff --git a/iot/latest/developerguide/iot-create-rule.md b/iot/latest/developerguide/iot-create-rule.md index 1b2cd2432..995a23cdb 100644 --- a//iot/latest/developerguide/iot-create-rule.md +++ b//iot/latest/developerguide/iot-create-rule.md @@ -22 +22 @@ Before you create an AWS IoT rule, you must create an IAM role with a policy tha -When you create a rule, be aware of how much data you're publishing on topics. If you create rules that include a wildcard topic pattern, they might match a large percentage of your messages. If this is the case, you might need to increase the capacity of the AWS resources used by the target actions. Also, if you create a republish rule that includes a wildcard topic pattern, you can end up with a circular rule that causes an infinite loop. +When you create a rule, be aware of how much data you're publishing on topics. If you create rules that include a wildcard topic pattern, they might match a large percentage of your messages. If this is the case, you might need to increase the capacity of the AWS resources used by the target actions. We recommend avoiding wildcard topic patterns in republish rules to prevent duplicate processing and reduce costs.