Does StartMessageMoveTask support SNS DLQs and cross-account targets?

Question

After reading the documentation for this new feature https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_StartMessageMoveTask.html I still have some questions:

1. Can the source queue be the DLQ for another service like SNS or Lambda?  Or it must be the DLQ for another SQS queue?
2. Can the destination queue be in a different AWS account (cross-account)?
3. If yes to #2, what IAM policy would be needed in the destination account to grant access?  (i.e. which principal, source attributes, etc.)

Accepted Answer

Here are the answers for your queries.
1/ The DLQ redrive works if the DLQ has received messages from any other SQS queue. If the DLQ has received messages directly from Lambda or SNS, the redrive to the source or custom queue is currently not supported. As a workaround, you can create a new queue and use the existing DLQ as the dead-letter queue for that new queue. After doing so, you can re-drive messages from your DLQ to any custom queue in SQS.
2/ DLQ doesn't support cross-account. DLQ must be under the same region and same account, so does redriving messages back to the source or custom queue.

Does StartMessageMoveTask support SNS DLQs and cross-account targets?

相關內容