As bagginsbill stated, poser and its queue manager find each other using UDP broadcast. Your problem, however, is not the UDP, this should be possible with most VPNs, it's the broadcast that gets in the way. You probably tried network rendering in a LAN using a common subnet. For example your machines have addresses 192.168.0.1 and 192.168.0.2; poser does a broadcast at 192.168.255.255, which each machine gets. When using an EC2 instance, it is neither in your local network, nor does it lie in a similar address range. So to get the data from poser to the QM in EC2, you have to do two things: First, the machines need to use the same address range (like 192.168.0.0/16 for example) and you have to create a path from your local network to amazon. The first one could be done by assigning a network address to the EC2 instance that matches your local network address (you must make this an additional address, not replace the old one or you will not be able to talk to your EC2 anymore). The second (creating a virtual local network) should be done with the VPN software you use; you have to tell it somehow to pass broadcasts through to the other network. This can be a little bit difficult depending on your VPN software you use. You should look within the options of the VPN software for broadcast forwarding. Easiest is probably when your VPN supports something called "ethernet bridging", or "802.3 tunneling" or something like that. It means that the VPN acts just like an additional network card for the computer. Note that i tried nothing of this with Poser, but i think this is what you should be looking for.