I assume that after the completion of the filtering operation it will be necessary to process the elements of the queue [entity]. Although several queues can certainly help, a more reliable way is to do the preprocessing and then (for example, filtering by sender ID), in my opinion, in an elegant way.
With the release of AWS Lambda, you can offload the filtering or preprocessing, and then click / place it in the appropriate places.
If you have your users who are queuing items, try the following approach.
You can try with 2 lambda functions [Feeder and Worker].
Feeder will have a scheduled lambda function , whose task is to take elements from SQS (if any) and click it as SNS theme (and keep doing this forever)
The worker will be involved in listening to the SNS topic, which will do data filtering [depending on the sender ID]. Past items can be moved to a new queue, and the rest can be undone.
It would be best if your users clicked objects directly on the SNS topic, and the lambda filter function could do the filtering directly.
source share