He doesn't seem to need a forever queue. Processing might take a while, but he just needs to get it processed once (and exactly once) and move on. Yes, if he wants to do event sourcing, then yes SQS would not suffice. But I don't think he needs that. But SQS seems to be a great choice.
Yeah we are already using SQS for a similar system that's currently in production. We don't need a forever queue as part of the goal is to keep the queue as empty as possible at all times. What is really important is making sure that only one job (with a distinct set of params) can be scheduled at one time and run by only worker at one time.
