In the good old license free times I used to beef up my renderpower by using linux nodes on Amazon AWS to get my jobs done in time. A small network of nodes was running while I was using my workstation as normal.
Especially the new nodes including tesla cards could be a nice temporal feature.
Only that the licences are bound to hardware is a bit of an issue, as I remember.
Of course one could use a renderfarm, but to me it is not the same amount of control.
Just as some input.
Hartmut
Indigo on AWS
Re: Indigo on AWS
I want to revive this topic.
What would be best way to utilise Amazon EC2 with Indigo. Buying more render nodes is not super happy solution because of licensing.
I guess best way would be to use floating license, but can not find any pricing about it. Did contact Indigo support once but never get definite answer.
What devs/support/sales can say about this?
What would be best way to utilise Amazon EC2 with Indigo. Buying more render nodes is not super happy solution because of licensing.
I guess best way would be to use floating license, but can not find any pricing about it. Did contact Indigo support once but never get definite answer.
What devs/support/sales can say about this?
Re: Indigo on AWS
As you can see, this topic never got attention. I used it back when indigo was in beta. You are probably right to use network licenses to jump back and forth between local and AWS EC2 nodes. M4 instances are just pretty nice...
Octane does offer licenced and setup machines on ec2, so you pay per use...
Octane does offer licenced and setup machines on ec2, so you pay per use...
Who is online
Users browsing this forum: No registered users and 3 guests