AWS eventbridge documentation change
Summary
Expanded error handling documentation to include 'invalid address or DNS lookup failure' as scenarios where events are sent to DLQ without retries.
Security assessment
The change clarifies error handling behavior but doesn't address security vulnerabilities or introduce security features. It's a reliability improvement with no security implications.
Diff
diff --git a/eventbridge/latest/userguide/eb-rule-dlq.md b/eventbridge/latest/userguide/eb-rule-dlq.md index c50a49aae..812baee5f 100644 --- a//eventbridge/latest/userguide/eb-rule-dlq.md +++ b//eventbridge/latest/userguide/eb-rule-dlq.md @@ -15 +15 @@ When you configure a DLQ for a target of a rule, EventBridge sends the events wi -Event errors are handled in different ways. Some events are dropped or sent to a DLQ without any retry attempts. For example, for errors that result from missing permissions to a target, or if a target resource that no longer exists, no retry attempts will happen until action is taken to resolve the underlying issue. EventBridge sends these events directly to the target DLQ, if you have specified one. +Event errors are handled in different ways. Some events are dropped or sent to a DLQ without any retry attempts. For example, for errors that result from missing permissions to a target, a target resource that no longer exists, or a target that cannot be found due to an invalid address or DNS lookup failure, no retry attempts will happen until action is taken to resolve the underlying issue. EventBridge sends these events directly to the target DLQ, if you have specified one.