Note
While AWS Portal can enable cloud rendering in Deadline 10, AWS Deadline Cloud is a newer offering that has been built specifically for the cloud. It is a fully managed service that does not require installation or maintenance of infrastructure (e.g., repository, database, or license server). Worker fleet auto-scaling, asset synching, and licensing are all managed natively within AWS by Deadline Cloud. See here for more information on Deadline Cloud and its capabilities.
Log Locations¶
You can find the logs for AWS Portal in the following locations
AWS Portal Link¶
Windows
%PROGRAMDATA%\Thinkbox\AWSPortalLink\
Linux
/var/log/Thinkbox/AWSPortalLink/
AWS Portal Asset Server¶
Windows
%PROGRAMDATA%\Thinkbox\AWSPortalAssetServer\logs\
Linux
/var/log/Thinkbox/AWSPortalAssetServer/
AWS Portal S3 Backed Cache Central Controller¶
The S3 Backed Cache Central Controller resides on the Gateway instance. To find the log, you will first need to connect to the Gateway instance. Once connected, the log can be found at the following path:
/var/log/Thinkbox/S3BackedCache/central_controller.log
AWS Portal Instance S3-Backed Cache Client Controller¶
The S3-Backed Cache Client resides on the spot fleet instances. To find the logs, you will first need to individually connect to each spot fleet instance. Once connected, the S3-Backed Cache Client logs can be found at the following platform-dependent paths:
Windows:
%PROGRAMDATA%\Thinkbox\S3backedCache\Client\Logs\worker_controller.log
Linux:
/mnt/dtu/worker_controller.log
