aws-sqs: add Queue.addDeadLetterQueue(dlq) for imported Queues

[lsmarsden]

Describe the feature

At the moment, if an SQS queue is imported via Queue.fromQueueArn(), the resulting queue cannot have a DLQ added to it via the CDK. DLQs can only be attached at creation time in the Queue.Builder or passing QueueProps to the constructor.

In a similar way to aws-lambda's addEventSource(eventSource), it would be nice to be able to add a DLQ to an existing SQS queue after it has been created, e.g. via an addDeadLetterQueue(dlq) method.

Use Case

I have a few SQS queues that have been created manually outside of my control. Unfortunately, there is no opportunity to delete these queues and recreate them directly in the CDK, so it has to be used as an import via Queue.fromQueueArn(). I'd like to set a DLQ on this queue via the CDK, and continue to use this queue in the rest of the CDK.

It may also be useful to decide to add a DLQ later on after the initial creation of non-imported queues, as an alternative to Queue.Builder.create(scope, id).deadLetterQueue(dlq).build();

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.84.0

Environment details (OS name and version, etc.)

MacOS Ventura 13

[pahud]

Queue.fromQueueArn() essentially import an existing Queue and CDK creates a reference for that and will not be able to modify or update it.

AFAIK, the DLQ is defined in RedrivePolicy prop of the Queue resource and CDK has no idea about the properties of the imported Queue resource. I am afraid this is probably not something the Queue L2 construct can control.

In general, when we import existing resources with CDK, especially for those created manually or outsides of CDK, CDK literally create references to those resources and basically CDK or cloudformation just can't modify or update those resources at all because they are not managed by CDK or cloudformation at all.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.