Python EventBridge Scheduler .create_schedule() RegEx Validation Failing

[fmg-kevin-kilroy]

Describe the bug

I'm trying to use a dead letter queue when creating a new Schedule however it is failing with the following error:

An error occurred (ValidationException) when calling the CreateSchedule operation: 1 validation error detected: Value 'arn:aws:sqs:ap-southeast-2:123456789123:retry-dlq.fifo' at 'target.deadLetterConfig.arn' failed to satisfy constraint: Member must satisfy regular expression pattern: arn:aws[a-z-]*:sqs:[a-z0-9\-]+:\d{12}:[a-zA-Z0-9\-_]+

Also, the current regex wouldn't support fifo queues that must end with .fifo

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

validation passes because it's a valid SQS Queue

Current Behavior

An error occurred (ValidationException) when calling the CreateSchedule operation: 1 validation error detected: Value 'arn:aws:sqs:ap-southeast-2:123456789123:fhs-px-mon-oncall-ack-retry-dlq.fifo' at 'target.deadLetterConfig.arn' failed to satisfy constraint: Member must satisfy regular expression pattern: arn:aws[a-z-]*:sqs:[a-z0-9\-]+:\d{12}:[a-zA-Z0-9\-_]+

Reproduction Steps

try to use the create_schedule() function with the Target parameter set to a valid SQS arn

Target={

            'DeadLetterConfig': {
                 'Arn': 'arn:.....'
            }, 

Possible Solution

arn:aws[a-z-]*:sqs:[a-z0-9\\-]+:\d{12}:[a-zA-Z0-9\-_\.]+

This would also support .fifo queues

Additional Information/Context

No response

SDK version used

1.35.77

Environment details (OS name and version, etc.)

Linux 5.15.167.4-microsoft-standard-WSL2

[tim-finnigan]

Thanks for reaching out. The User Guide for EventBridge Scheduler notes:

EventBridge Scheduler does not support using a FIFO queue as your schedule's DLQ.

Also the Boto3 create_schedule command makes a request to the underlying CreateSchedule API, and the ValidationError is being return directly from that API. For DeadLetterConfig specifically, the regex is referenced here: https://docs.aws.amazon.com/scheduler/latest/APIReference/API_DeadLetterConfig.html. For bugs involving the service API we could reach out to the service team for review, but in this case based on the documentation this appears to be the expected behavior. If we're missing anything please let us know.