So @JakeS I’m almost certain that you would see that error go away if you ensure you run hserver on boot/user data for cloud, and you could try and run hython first before you try anything on deadline to test for good measure. Bobo informed me that when UBL takes over it temporarily redirects hserver to the local port and license forwarder (with the arg -S). When the job is done, the connection is restored to whatever previous license server you have configured (if any). Still hserver MUST be running because the hserver -S command cannot function until you have executed hserver first by itself. This strikes me as an oversight, and I think @thinkbox should start hserver if it is not already started.
I had to do a little dance in my case, with a 10 second delay and running hserver twice in user data on EC2 for some strange reason, but I hope one day this is not necessary: