AWS Thinkbox Discussion Forums

Deadline License Forwarder but on Deadline Cloud

Hello,

we succesfully setup an aws deadline cloud customer managed fleet following this guide.

The last missing part is how we can license redshift. We want to use a usage based licensing model and bought a couple of hours from the thinkbox marketing place.

There is a whole page that explains how you can setup the UBL licenses from the marketplace. But the instructions are all for classic deadline and not deadline cloud.

We want it to work on our existing aws deadline cloud setup so our customer managed fleet can checkout the licenses.

The license forwarder seems to offer a solution for what we need, but requires a full local deadline setup with a repository and all.

Is this the way to go for us and how would we best set this up with our aws deadline cloud fleet?

With redshift for instance you can set the redshift_LICENSE env variable and point it to an RLM server.

If we get the license forwarder running would we define redshift_LICENSE on our ec2 instances and point it to the license forwarder?

If anyone has some tipps or general advice how to solve this would be much appreciated.

I don’t think that’s going to work as that’s not how the UBL works. From my understanding you’d need to run a DeadlineCloud job, to launch an instance which is running DeadlineOriginal which connects to the original repo and accepts a job from there. seems a total faff.

You could use the Redshift login licenses but it looks like they only sell annual licenses now, which defeats the point again. It looks like the regular Redshift UBL licenses are running out this year (from the logs using DeadlineOriginal) so hopefully both versions of Deadline UBL will get an update by then.

1 Like

Hey @anthonygelatka

yeah in the meantime i got an asnwer from the deadline staff as well that deadline redshift ubl is not possible in deadline cloud. We’d have to use deadline 10 classic for that.

1 Like
Privacy | Site terms | Cookie preferences