Hello
We’ve got a VPC set up with Amazon, which keeps things more secure. Deadline can see EC2 instances in our VPC happily, but cloning them in Deadline automatically gives new instances public IPs – which we don’t want, we just want more machines in our VPC.
Any ideas?
Thanks
Tom
Hey Tom,
So we actually just discovered this same issue the other day while working with our own VPC that we’ve recently set up for testing. The problem is that we’re starting the instances using the libcloud plugin, which doesn’t offer any kind of control over whether or not the instances are spun up using VPC.
Unfortunately, since our use of the libcloud plugin is in our own UI code, there isn’t much you can do about this for the moment.
The good news is that for 6.1, we’re both moving away from libcloud to a plugin that lets us do VPC stuff (boto), and exposing the cloud control stuff as a separate Deadline plugin, so end users will be able to tinker with the instance startup behaviour if they run into issues such as this.
If you need to access this stuff sooner rather that later, I believe we’ll be announcing beta plans for 6.1 soonish, so stay tuned for details!
Cheers,
Thanks Jon. I’ll watch out for the next beta.
Tom
Hi Jon
Just installed the 6.1 Beta, which has the same issue. Is this something that’ll only be supported in VMX?
Thanks
Tom
In the current beta build, yes, but the plan is to have it work for the regular cloud hookups in Deadline as well.
We just haven’t changed the Cloud panel to use the new Cloud Plugins we set up for VMX, yet. It is one of our higher priority items, so it should hopefully make it into the Beta soon. Probably sooner rather than later, since you’re interested in testing this out 
Cheers,
Great news, thanks Jon. Looking forward to giving it a spin.
Tom