I think the short answer is there's no Amazon specific way to handle this. The Amazon support engineer that answers the SO question you linked kind of mentions that. You have distributed locking problem rather and a specific "Cron" or scheduling problem. If you lock the processes that need to be locked and treated as singletons then the issue goes away.
My experience with Amazon On-demand Queues ( SQS ) and Workflow ( SWF ) has been that you are likely better off rolling your own on an EC2 instance. *In general*, the on-demand services make financial sense I believe when your workload fluctuates greatly. Eg. You have almost zero queue traffic now but may need a few servers in a split second. With highly unpredictable workloads it doesn't make a lot of sense building out infrastructure sense you don't know how much you'll need, and when you'll need it. For queues I'd recommend Rabbit MQ as a replacement for SQS. Gearman, etc are also popular.
Business Web Development
From: [address removed] [mailto:[address removed]] On Behalf Of GC
Sent: Monday, February 25,[masked]:36 PM
To: [address removed]
Subject: [newtech-1] AWS Cron Jobs
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by GC ([address removed]) from NY Tech Meetup.
To learn more about GC, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, POB 4668 #37895 NY NY USA 10163 | [address removed]