What does this Amazon Web Services Solution do?
Building a rendering farm in the cloud environment is never easy, and it could take days or weeks to do so. The Cloud Rendering Farm Solution enables you to build and deploy a rendering farm on Amazon Web Services Cloud with just one-click.
This solution is designed and built around Thinkbox Deadline, which provides flexibility and a wide range of compute management options, giving you the freedom to easily access any combination of on-premises, hybrid or cloud-based resources for your rendering, render management and processing needs.
No matter you need to build a rendering farm on cloud, or plan to use cloud resources to expand local rendering capabilities, you can use this solution to speed up the process, save time and cost.
Amazon Web Services Solution overview
This solution helps you easily build a cloud rendering farm for you from three aspects:
1. Rendering task scheduling platform, using Deadline. Thinkbox Deadline is a hassle-free hybrid administration and compute management software for Windows, Linux, and mac OS based render farms, supporting more than 80 different content creation applications out of the box.
2. Remote desktop, used to graphically manage rendering tasks and visually view results, generated by NICE DCV. NICE DCV is a high-performance remote display protocol that provides you with a secure way to deliver remote desktops and application streaming from any cloud or data center to any device, over varying network conditions.
3. Media asset management platform, used for sharing project files and material files. This solution currently supports EFS and JuiceFS, and will support more shared file system services or products in the future.
The Amazon CloudFormation template of this solution will automatically deploy and configure a set of cloud rendering architecture, which includes services such as Amazon VPC, Amazon EC2, and services such as Amazon EFS or Amazon S3 based on your choice of shared file system. This solution provides a graphical interface through the NICE DCV remote desktop, and pre-configured deadline monitoring software for you to view and manage rendering tasks. Additionally, this solution will create a public subnet and a private subnet in each of the two availability zones, and create a NAT Gateway in each public subnet so that EC2 instances in the private subnet can actively access the Internet to download resources. The created EC2 instances are divided into the following four types:
1. Deadline Monitor: deployed in a public subnet, allowing SSH and DCV access from the Internet, used for graphically managing rendering tasks, viewing rendering results, transferring files, and logging into other EC2 instances as a bastion.
2. Deadline Repository: Deployed in a private subnet, used to schedule all rendering tasks to working nodes, and store the status and logs of all tasks and nodes.
3. Deadline Worker: Deployed in a private subnet, install different rendering software, and undertake rendering tasks.
4. Deadline License Server: deployed in a private subnet, used to authorize all nodes using Deadline software.
The software in each node, access permissions between nodes, and file system mounting permissions have been automatically pre-configured. What you need to do is just to install the rendering software you need in the working node and upload the corresponding asset files to the shared file system to start rendering.
Support multiple shared file systems
Security Best Practice
Browse our portfolio of Amazon Web Services-built solutions to common architectural problems.
Find Amazon Web Services certified consulting and technology partners to help you get started.
Sign-up and start exploring our services.