Since you are already using aws, for something like this you couldconsider using AWS SQS to add a queue between the two hosts and communicate thru it instead of directly.
Using SQS, it would be easy to write a script to add messages to the SQS queue when something needs to be run on the other host, and equally easy for the second host to poll the queue looking for messages.
Adding a queue between the two hosts decouples them, and adds a bit of fault tolerance (i.e. one of the hosts could go off line for a bit without the messages being lost), and possibly gives you the ability to scale up if you need to a bit easier (for example, if you ever needed multiple instances at aws processing jobs from the other host you could just add them and tell them to also poll the same queue, as opposed to building in a 1-1 'always on' dependency between the two.
Lots of different ways to skin this cat, so maybe the approach above is overkill in your case, but thought I'd throw it out there as something to consider.