In order to support certain workers to be triggered only on certain stacks (e.g. prod) we need a way so that the SQS message that triggers the worker is not sent by all the stacks, but rather is trigger externally. We can implement a web service to do this (since the queues are bound to the stack we cannot directly send a msg to SQS) that allows to send a message to an SQS queue.
This will allow us to avoid having duplicate output in staging vs prod (e.g. sending scheduled messages) that might reach the end user.
Additionally we should add generic machinery to setup a worker that acts as a remote trigger on a particular queue on a configured stack.