AWS scheduler documentation change
Summary
Added note about universal target input validation limitations and DLQ behavior
Security assessment
Documents system behavior around input validation gaps but doesn't disclose a security flaw. Focuses on error handling rather than security controls.
Diff
diff --git a/scheduler/latest/UserGuide/configuring-schedule-dlq.md b/scheduler/latest/UserGuide/configuring-schedule-dlq.md index 4cfa4cce1..8749c8893 100644 --- a//scheduler/latest/UserGuide/configuring-schedule-dlq.md +++ b//scheduler/latest/UserGuide/configuring-schedule-dlq.md @@ -230,0 +231,4 @@ In the preceding example, we can determine, based on the error code, and the err +###### Note + +If you use [universal targets](./managing-targets-universal.html), be aware that EventBridge Scheduler does not validate the contents of the `Input` field at schedule creation time. A schedule with invalid input parameters will be created successfully but will fail on every invocation. The DLQ message will contain the error code and message from the target service, which can help you identify the invalid parameter. For more information, see [Invalid universal target input configurations](./troubleshooting.html#troubleshooting-usi-target-input). +