Rather than helping them develop an entirely new way of doingCloud303 built a Windows Active Directory based network in AWS in a new VPC that they deployed next to the data they were already storing in AWS. The VPC contains a domain controller (to handle authentication), a file server (for exporting data from S3 to a higher speed solution that the nodes can run off of), a client-server (for building projects), and a coordination server (for coordinating all the projects and sending them to the nodes for rendering) and six rendering nodes, all based on Windows. Cloud303 also streamlined the process by automating the coordination server and rendering nodes, so from the point of view of the user, they’re just using Metashape on a single machine, but in the background, this fast, reliable, efficient system is available. With Metashape ostensibly running as a service, complicated management is abstracted away. Additionally, the system was designed so the nodes could be turned on and off from the AWS CLI using a powershell application written by Cloud303. That way, the fleet would only be running when it’s in use, which helps optimize costs. things, Cloud303 was willing to take the time to learn how Silent Falcon’s process was already working, and expand upon that to make it better. This was the main appeal of Cloud303 when Silent Falcon was looking for an AWS partner to work with..