Set up Deadline Cloud submitters
This process is for administrators and artists who want to install, set up, and launch the
AWS Deadline Cloud submitter. A Deadline Cloud submitter is a digital
content creation (DCC) plugin. Artists use it to submit jobs from a third-party DCC
interface that they're familiar with.
This process must be completed on all workstations that artists will use for
submitting renders.
Each workstation must have the DCC installed before installing the corresponding
submitter. For example, if you want to download the Deadline Cloud submitter for Blender, you need to
have Blender already installed on your workstation.
Step 1: Install the Deadline Cloud submitter
The following sections guide you through the steps to install the Deadline Cloud
submitter.
Download the submitter installer
Before you can install the Deadline Cloud submitter, you must download the submitter
installer. Currently, the Deadline Cloud submitter installer only supports
Windows and Linux.
-
Sign in to the AWS Management Console and open the Deadline Cloud console.
-
From the side navigation pane, choose
Downloads.
-
Locate the Deadline Cloud submitter installer
section.
-
Select the installer for your computer's operating
system, and then choose Download.
(Optional) Verify the authenticity of the
downloaded software
To verify that the software you downloaded is authentic, use the following
procedure for either Windows or Linux. You might want
to do this to ensure no one has tampered with the files during or after the download
process.
You can use these instructions to first verify the installer, and then verify the
Deadline Cloud monitor after you download it in Step 2: Install and set up
Deadline Cloud monitor.
- Windows
-
To verify the authenticity of your downloaded files, complete the
following steps.
-
In the following command, replace
file
with the
file that you want to verify. For example,
C:\PATH\TO\MY\
DeadlineCloudSubmitter-windows-x64-installer.exe
. Also, replace
signtool-sdk-version
with the version of the SignTool SDK installed.
For example, 10.0.22000.0
.
"C:\Program Files (x86)\Windows
Kits\10\bin\signtool-sdk-version
\x86\signtool.exe"
verify /vfile
-
For example, you can verify the Deadline Cloud submitter installer file
by running the following command:
"C:\Program Files (x86)\Windows
Kits\10\bin\10.0.22000.0\x86\signtool.exe" verify /v
DeadlineCloudSubmitter-windows-x64-installer.exe
- Linux
-
To verify the authenticity of your downloaded files, use the
gpg
command line tool.
-
Import the OpenPGP
key by running the following
command:
gpg --import --armor <<EOF
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBGX6GQsBEADduUtJgqSXI+q76O6fsFwEYKmbnlyL0xKvlq32EZuyv0otZo5L
le4m5Gg52AzrvPvDiUTLooAlvYeozaYyirIGsK08Ydz0Ftdjroiuh/mw9JSJDJRI
rnRn5yKet1JFezkjopA3pjsTBP6lW/mb1bDBDEwwwtH0x9lV7A03FJ9T7Uzu/qSh
qO/UYdkafro3cPASvkqgDt2tCvURfBcUCAjZVFcLZcVD5iwXacxvKsxxS/e7kuVV
I1+VGT8Hj8XzWYhjCZxOLZk/fvpYPMyEEujN0fYUp6RtMIXve0C9awwMCy5nBG2J
eE2Ol5DsCpTaBd4Fdr3LWcSs8JFA/YfP9auL3NczOozPoVJt+fw8CBlVIXO0J7l5
hvHDjcC+5v0wxqAlMG6+f/SX7CT8FXK+L3iOJ5gBYUNXqHSxUdv8kt76/KVmQa1B
Akl+MPKpMq+lhw++S3G/lXqwWaDNQbRRw7dSZHymQVXvPp1nsqc3hV7KlOM+6s6g
1g4mvFY4lf6DhptwZLWyQXU8rBQpojvQfiSmDFrFPWFi5BexesuVnkGIolQoklKx
AVUSdJPVEJCteyy7td4FPhBaSqT5vW3+ANbr9b/uoRYWJvn17dN0cc9HuRh/Ai+I
nkfECo2WUDLZ0fEKGjGyFX+todWvJXjvc5kmE9Ty5vJp+M9Vvb8jd6t+mwARAQAB
tCxBV1MgRGVhZGxpbmUgQ2xvdWQgPGF3cy1kZWFkbGluZUBhbWF6b24uY29tPokC
VwQTAQgAQRYhBLhAwIwpqQeWoHH6pfbNPOa3bzzvBQJl+hkLAxsvBAUJA8JnAAUL
CQgHAgIiAgYVCgkICwIDFgIBAh4HAheAAAoJEPbNPOa3bzzvKswQAJXzKSAY8sY8
F6Eas2oYwIDDdDurs8FiEnFghjUEO6MTt9AykF/jw+CQg2UzFtEyObHBymhgmhXE
3buVeom96tgM3ZDfZu+sxi5pGX6oAQnZ6riztN+VpkpQmLgwtMGpSMLl3KLwnv2k
WK8mrR/fPMkfdaewB7A6RIUYiW33GAL4KfMIs8/vIwIJw99NxHpZQVoU6dFpuDtE
1OuxGcCqGJ7mAmo6H/YawSNp2Ns80gyqIKYo7o3LJ+WRroIRlQyctq8gnR9JvYXX
42ASqLq5+OXKo4qh81blXKYqtc176BbbSNFjWnzIQgKDgNiHFZCdcOVgqDhwO15r
NICbqqwwNLj/Fr2kecYx180Ktpl0jOOw5IOyh3bf3MVGWnYRdjvA1v+/CO+55N4g
z0kf50Lcdu5RtqV10XBCifn28pecqPaSdYcssYSRl5DLiFktGbNzTGcZZwITTKQc
af8PPdTGtnnb6P+cdbW3bt9MVtN5/dgSHLThnS8MPEuNCtkTnpXshuVuBGgwBMdb
qUC+HjqvhZzbwns8dr5WI+6HWNBFgGANn6ageYl58vVp0UkuNP8wcWjRARciHXZx
ku6W2jPTHDWGNrBQO2Fx7fd2QYJheIPPAShHcfJO+xgWCof45D0vAxAJ8gGg9Eq+
gFWhsx4NSHn2gh1gDZ41Ou/4exJ1lwPM
=uVaX
-----END PGP PUBLIC KEY BLOCK-----
EOF
-
Determine whether to trust the OpenPGP
key. Some
factors to consider when deciding whether to trust the above key
include the following:
-
The internet connection you’ve used to obtain the GPG
key from this website is secure.
-
The device that you are accessing this website on is
secure.
-
AWS has taken measures to secure the hosting of the
OpenPGP
public key on this
website.
-
If you decide to trust the OpenPGP key, edit
the key to trust with gpg
similar to the following
example:
$ gpg --edit-key 0xB840C08C29A90796A071FAA5F6CD3CE6B76F3CEF
gpg (GnuPG) 2.0.22; Copyright (C) 2013 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub 4096R/4BF0B8D2 created: 2023-06-23 expires: 2025-06-22 usage: SCEA
trust: unknown validity: unknown
[ unknown] (1). AWS Deadline Cloud example@example.com
gpg> trust
pub 4096R/4BF0B8D2 created: 2023-06-23 expires: 2025-06-22 usage: SCEA
trust: unknown validity: unknown
[ unknown] (1). AWS Deadline Cloud aws-deadline@amazon.com
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y
pub 4096R/4BF0B8D2 created: 2023-06-23 expires: 2025-06-22 usage: SCEA
trust: ultimate validity: unknown
[ unknown] (1). AWS Deadline Cloud aws-deadline@amazon.com
Please note that the shown key validity is not necessarily correct
unless you restart the program.
gpg> quit
-
Verify the Deadline Cloud submitter installer
To verify the Deadline Cloud submitter installer, complete the
following steps:
-
Return to the Deadline Cloud console
Downloads page and download the
signature file for the Deadline Cloud submitter installer.
-
Verify the signature of the Deadline Cloud submitter installer
by running:
gpg --verify ./DeadlineCloudSubmitter-linux-x64-installer.run.sig ./DeadlineCloudSubmitter-linux-x64-installer.run
-
Verify the Deadline Cloud monitor
You can verify the Deadline Cloud monitor download using signature files
or platform specific methods. For platform specific methods,
see the Linux (Debian) tab, the Linux (RPM)
tab, or the Linux (AppImage) tab based on
your downloaded file type.
To verify the Deadline Cloud monitor desktop application with signature files,
complete the following steps:
-
Return to the Deadline Cloud console
Downloads page and download the
corresponding .sig file, and then run
For .deb:
gpg --verify ./deadline-cloud-monitor_<APP_VERSION>
_amd64.deb.sig ./deadline-cloud-monitor_<APP_VERSION>
_amd64.deb
For .rpm:
gpg --verify ./deadline-cloud-monitor_<APP_VERSION>
_x86_64.deb.sig ./deadline-cloud-monitor_<APP_VERSION>
_x86_64.rpm
For .AppImage:
gpg --verify ./deadline-cloud-monitor_<APP_VERSION>
_amd64.AppImage.sig ./deadline-cloud-monitor_<APP_VERSION>
_amd64.AppImage
-
Confirm that the output looks similar to the
following:
gpg: Signature made Mon Apr 1 21:10:14 2024
UTC
gpg: using RSA key
B840C08C29A90796A071FAA5F6CD3CE6B7
If the output contains the phrase Good signature
from "AWS Deadline Cloud"
, it means that the
signature has successfully been verified and you can run
the Deadline Cloud monitor installation script.
- Linux (AppImage)
-
To verify packages that use a Linux .AppImage binary, first complete
steps 1-3 in the Linux tab, then complete the following steps.
-
From the AppImageUpdate page in GitHub, download the
validate-x86_64.AppImage file.
-
After downloading the file, to add execute permissions, run
the following command.
chmod a+x ./validate-x86_64.AppImage
-
To add execute permissions, run the following command.
chmod a+x ./deadline-cloud-monitor_<APP_VERSION>
_amd64.AppImage
-
To verify the Deadline Cloud monitor signature, run the following
command.
./validate-x86_64.AppImage ./deadline-cloud-monitor_<APP_VERSION>
_amd64.AppImage
If the output contains the phrase Validation
successful
, it means that the signature has
successfully been verified and you can safely run the Deadline Cloud monitor
installation script.
- Linux (Debian)
-
To verify packages that use a Linux .deb binary, first complete
steps 1-3 in the Linux tab.
dpkg is the core package management tool in most
debian based Linux distributions. You
can verify the .deb file with the tool.
-
From the Deadline Cloud console
Downloads page, download the Deadline Cloud monitor .deb
file.
-
Replace <APP_VERSION>
with
the version of the .deb file you want to verify.
dpkg-sig --verify deadline-cloud-monitor_<APP_VERSION>
_amd64.deb
-
The output will be similar to:
ProcessingLinux deadline-cloud-monitor_<APP_VERSION>
_amd64.deb...
GOODSIG _gpgbuilder B840C08C29A90796A071FAA5F6CD3C 171200
-
To verify the .deb file, confirm that GOODSIG
is
present in the output.
- Linux (RPM)
-
To verify packages that use a Linux .rpm binary, first complete
steps 1-3 in the Linux tab.
-
From the Deadline Cloud console
Downloads page, download the Deadline Cloud monitor .rpm
file.
-
Replace <APP_VERSION>
with
the version of the .rpm file to verify.
gpg --export --armor "Deadline Cloud" > key.pub
sudo rpm --import key.pub
rpm -K deadline-cloud-monitor-<APP_VERSION>
-1.x86_64.rpm
-
The output will be similar to:
deadline-cloud-monitor-deadline-cloud-monitor-<APP_VERSION>
-1.x86_64.rpm-1.x86_64.rpm: digests signatures OK
-
To verify the .rpm file, confirm that digests signatures
OK
is in the output.
Install the Deadline Cloud
submitter
You can install a Deadline Cloud submitter with Windows or
Linux. With the installer, you can install the following
submitters:
Software |
Supported versions |
Windows installer |
Linux installer |
Adobe After Effects |
2024, 2025 |
Included |
Not included |
Autodesk Arnold for Maya |
7.1, 7.2 |
Included |
Included |
Autodesk Maya |
2023, 2024, 2025 |
Included |
Included |
Blender |
3.6, 4.2 |
Included |
Included |
KeyShot Studio |
2023, 2024 |
Included |
Not included |
Maxon Cinema 4D |
2024, 2025 |
Included |
Not included |
Nuke |
15 |
Included |
Included |
SideFX Houdini |
19.5, 20, 20.5 |
Included |
Included |
Unreal Engine |
5.2, 5.3, 5.4 |
Included |
Not included |
You can install other submitters not listed here. We use Deadline Cloud libraries to build
submitters. Some of the submitters include 3ds Max and Rhino. You can find the
source code for these libraries and submitters in the aws-deadline GitHub
organization.
- Windows
-
-
In a file browser, navigate to the folder where the installer
downloaded, and then select
DeadlineCloudSubmitter-windows-x64-installer.exe
.
-
If a Windows protected your PC
pop-up displays, choose More
info.
-
Choose Run anyway.
-
After the AWS Deadline Cloud Submitter Setup Wizard opens, choose
Next.
-
Choose the installation scope by completing one of the
following steps:
-
To install for only the current user, choose
User.
-
To install for all users, choose
System.
If you choose System, you must
exit the installer and re-run it as an administrator by
completing the following steps:
-
Right-click on
DeadlineCloudSubmitter-windows-x64-installer.exe
,
and then choose Run as
administrator.
-
Enter your administrator credentials, and then
choose Yes.
-
Choose System for the
installation scope.
-
After selecting the installation scope, choose
Next.
-
Choose Next again to accept the
installation directory.
-
Select Integrated submitter for
Nuke, or whichever submitter you
want to install.
-
Choose Next.
-
Review the installation, and choose
Next.
-
Choose Next again, and then choose
Finish.
- Linux
-
The Deadline Cloud integrated Nuke installer for
Linux and Deadline Cloud monitor can only be installed on
Linux distributions with at least GLIBC 2.31.
-
Open a terminal window.
-
To do a system install of the installer, enter the command
sudo -i
and press
Enter to become root.
-
Navigate to the location where you downloaded the
installer.
For example, cd
/home/USER
/Downloads
.
-
To make the installer executable, enter chmod +x
DeadlineCloudSubmitter-linux-x64-installer.run
.
-
To run the Deadline Cloud submitter installer, enter
./DeadlineCloudSubmitter-linux-x64-installer.run
.
-
When the installer opens, follow the prompts on your screen to
complete the Setup Wizard.
Step 2: Install and set up
Deadline Cloud monitor
You can install the Deadline Cloud monitor desktop application with Windows or Linux.
- Windows
-
-
If you haven't already, sign in to the AWS Management Console and open the
Deadline Cloud console.
-
From the left navigation pane, choose monitor
Downloads.
-
In the Deadline Cloud monitor section, select the file for
your computer's operating system.
-
To download the Deadline Cloud monitor, choose
Download.
To perform a silent install, use the following command:
DeadlineCloudMonitor_VERSION_x64-setup.exe /S
By default the monitor is installed in
C:\Users{username}\AppData\Local\DeadlineCloudMonitor
. To
change the installation directory, use this command instead:
DeadlineCloudMonitor_VERSION_x64-setup.exe /S /D={InstallDirectory}
- Linux (AppImage)
-
To install Deadline Cloud monitor AppImage on Debian distros
-
Download the latest Deadline Cloud monitor AppImage.
-
This step is for Ubuntu 22 and up. For other versions of
Ubuntu, skip this step.
To install libfuse2, enter:
sudo apt udpate
sudo apt install libfuse2
-
To make the AppImage executable, enter:
chmod a+x deadline-cloud-monitor_<APP_VERSION>
_amd64.AppImage
- Linux (Debian)
-
To install Deadline Cloud monitor Debian package on Debian distros
-
Download the latest Deadline Cloud monitor Debian package.
-
This step is for Ubuntu 22 and up. For other versions of
Ubuntu, skip this step.
To install libssl1.1, enter:
wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2_amd64.deb
sudo apt install ./libssl1.1_1.1.1f-1ubuntu2_amd64.deb
-
To install the Deadline Cloud monitor Debian package, enter:
sudo apt update
sudo apt install ./deadline-cloud-monitor_<APP_VERSION>
_amd64.deb
-
If the install fails on packages that have unmet dependencies, fix
the broken packages and then run the following commands.
sudo apt --fix-missing update
sudo apt update
sudo apt install -f
- Linux (RPM)
-
To install Deadline Cloud monitor RPM on Rocky Linux 9 or Alma
Linux 9
-
Download the latest Deadline Cloud monitor RPM.
-
Add the extra packages for the Enterprise Linux 9
repository:
sudo dnf install epel-release
-
Install compat-openssl11 for the libssl.so.1.1 dependency:
sudo dnf install compat-openssl11 deadline-cloud-monitor-<VERSION>
-1.x86_64.rpm
To install Deadline Cloud monitor RPM on Red Hat Linux 9
-
Download the latest Deadline Cloud monitor RPM.
-
Enable the CodeReady Linux Builder
repository:
subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms
-
Install the extra packages for Enterprise
RPM:
sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
-
Install compat-openssl11 for the libssl.so.1.1 dependency:
sudo dnf install compat-openssl11 deadline-cloud-monitor-<VERSION>
-1.x86_64.rpm
To install Deadline Cloud monitor RPM on Rocky Linux 8, Alma
Linux 8, or Red Hat Linux 8
-
Download the latest Deadline Cloud monitor RPM.
-
Install the Deadline Cloud monitor:
sudo dnf install deadline-cloud-monitor-<VERSION>
-1.x86_64.rpm
After you complete the download, you can verify the authenticity of the downloaded
software. You might want to do this to ensure no one has tampered with the files during
or after the download process. See Verify authenticity of downloaded software in Step
1.
After downloading Deadline Cloud monitor and verifying the authenticity, use the following procedure
to set up the Deadline Cloud monitor.
To set up Deadline Cloud monitor
-
Open Deadline Cloud monitor.
-
When prompted to create a new profile, complete the following steps.
-
Enter your monitor URL into the URL input, which looks like
https://MY-MONITOR
.deadlinecloud.amazonaws.com/
-
Enter a Profile name.
-
Choose Create Profile.
Your profile is created and your credentials are now shared with any
software that uses the profile name that you created.
-
After you create the Deadline Cloud monitor profile, you can't change the profile name or the
studio URL. If you need to make changes, do the following instead:
-
Delete the profile. In the left navigation pane, choose
Deadline Cloud monitor > Settings
> Delete.
-
Create a new profile with the changes that you want.
-
From the left navigation pane, use the >Deadline Cloud monitor option to
do the following:
-
Close the Deadline Cloud monitor window. It continues to run in the background and sync your
credentials every 15 minutes.
-
For each digital content creation (DCC) application that you plan to use for
your rendering projects, complete the following steps:
-
From your Deadline Cloud submitter, open the Deadline Cloud workstation
configuration.
-
In the workstation configuration, select the profile that you created
in the Deadline Cloud monitor. Your Deadline Cloud credentials are now shared with this DCC and
your tools should work as expected.
Step 3: Launch the Deadline Cloud submitter
The following example shows how to install the Blender submitter. You
can install other submitters using the instructions in Supported submitters.
To launch the Deadline Cloud submitter in Blender
-
Open Blender.
-
Choose Edit, then Preferences. Under
File Paths choose Script
Directories, then choose Add. Add a script
directory for the python folder where the Blender submitter was
installed:
Windows:
%USERPROFILE%\DeadlineCloudSubmitter\Submitters\Blender\python\
Linux:
~/DeadlineCloudSubmitter/Submitters/Blender/python/
-
Restart Blender.
-
Choose Edit, then Preferences. Next,
choose Add-ons, then search for Deadline Cloud for
Blender. Select the checkbox to enable the
add-on.
-
Open a Blender scene with dependencies that exist within the
asset root directory.
-
In the Render menu, select the Deadline Cloud dialog.
-
If you are not already authenticated in the Deadline Cloud submitter, the
Credentials Status shows as
NEEDS_LOGIN.
-
Choose Login.
-
A login browser window displays. Log in with your user
credentials.
-
Choose Allow. You are now logged in and the
Credentials Status shows as
AUTHENTICATED.
-
Choose Submit.