I have been using using RemoteBatchSubmit on AWS. Occasionally I have to kill a job using RemoteBatchJobAbort. I have found that whenever I do this I can't get AWS to accept a follow-up job; the new job just seems to sit in the Runnable status. To over come the problem I've had to delete the batch stack and generate a new one using the Wolfram template. Maybe I haven't waited long enough before trying a new job after aborting a calculation? Is there some way to manually reset things on AWS to prepare it for a new job, or do I just need to be more patient and wait longer before submitting my next project?