I can confirm that Poser cannot distribute individual render buckets over the net (only Bryce does that, IMO, and mojoWorld could do a limited bit that). Similary, Poser does not split up animations within a CPU, it's one frame at a time, not frames in parallel. So: long lasting renders and especially animations can be forked out, as long as animations render to separate images. Personally I run them as a QM in background low priority job utilizing CPU idle time.

The Queue manager says it uses ports 4418 and 11523 to communicate. I guess the EC2 machine act on those ports, and an active QM at that side should do (part of the) the job. I'm not sure UDP supports that, the EC2 machine just should act as another machine in the local / render network. Interesting though, keep posting please.

Given the rates, buying another high CPU high RAM (low disk low video) machine seems to be more cost-effective than cloud rendering. As it stands right now.
Point is: there is not only a usage fee per minute or so, but a monthly fee as well.

- - - - - 

Usually I'm wrong. But to be effective and efficient, I don't need to be correct or accurate.

visit www.aRtBeeWeb.nl (works) or Missing Manuals (tutorials & reviews) - both need an update though