# Getting started with Deadline Cloud
To create a farm in AWS Deadline Cloud, you can use either the [Deadline Cloud console](https://console.aws.amazon.com/deadlinecloud/home) or the AWS Command Line Interface (AWS CLI). Use the console for a guided experience creating the farm, including queues and fleets. Use the AWS CLI to work directly with the service, or for developing your own tools that work with Deadline Cloud.
To create a farm and use the Deadline Cloud monitor, set up your account for Deadline Cloud. You only need to set up the Deadline Cloud monitor infrastructure once per account. From your farm, you can manage your project, including user access to your farm and its resources.
To create a farm with minimal resources to accept jobs, select **Quickstart** in the console home page. **[Set up the Deadline Cloud monitor](monitor-onboarding.md)** walks you through those steps. These farms start with a queue and a fleet that are automatically associated. This approach is a convenient way to create sandbox style farms to experiment in.
**Topics**
+ [Set up your AWS account](setting-up.md)
+ [Set up the Deadline Cloud monitor](monitor-onboarding.md)
+ [Set up your workstation](submitter.md)
# Set up your AWS account
Set up your AWS account to use AWS Deadline Cloud.
If you do not have an AWS account, complete the following steps to create one.
**To sign up for an AWS account**
1. Open [https://portal.aws.amazon.com/billing/signup](https://portal.aws.amazon.com/billing/signup).
1. Follow the online instructions.
Part of the sign-up procedure involves receiving a phone call or text message and entering a verification code on the phone keypad.
When you sign up for an AWS account, an *AWS account root user* is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to a user, and use only the root user to perform [tasks that require root user access](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks).
When you first create an AWS account, you begin with one sign-in identity that has complete access to all AWS services and resources in the account. This identity is called the AWS account *root user* and is accessed by signing in with the email address and password that you used to create the account.
**Important**
We strongly recommend that you don't use the root user for your everyday tasks. Safeguard your root user credentials and use them to perform the tasks that only the root user can perform. For the complete list of tasks that require you to sign in as the root user, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*.
# Set up the Deadline Cloud monitor
To get started, you'll need to create your Deadline Cloud farm infrastructure, including a monitor, queue, and fleet. You can also perform additional, optional steps including adding groups and users, choosing a service role, and adding tags to your resources.
## Step 1: Create your monitor
The Deadline Cloud monitor uses AWS IAM Identity Center to authorize users. By default, the IAM Identity Center instance that you use for Deadline Cloud must be in the same AWS Region as the monitor. However, if you have Multi-Region support enabled in IAM Identity Center, you can create a monitor in a different Region. For more information, see [What is AWS IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html). If your console is using a different Region when you create the monitor, you'll get a reminder to change to the IAM Identity Center Region.
Your monitor's infrastructure consists of the following components:
+ **Monitor name**: The **Monitor name** is how you can identify your monitor — for example *AnyCompany monitor*. Your monitor's name also determines your **monitor URL**.
+ **Monitor URL**: You can access your monitor by using the **Monitor URL**. The URL is based on the **Monitor name** — for example *https://anycompanymonitor.awsapps.com*.
+ **AWS Region**: The **AWS Region** is the physical location for a collection of AWS data centers. When you set up your monitor, the Region defaults to the closest location to you. We recommend changing the Region so it is located closest to your users. This reduces lag and improves data transfer speeds. By default, AWS IAM Identity Center must be enabled in the same AWS Region as Deadline Cloud, unless you have Multi-Region support enabled in IAM Identity Center. For more information, see [What is AWS IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html).
**Important**
You can't change your Region after you finish setting up Deadline Cloud.
Complete the tasks in this section to configure your monitor's infrastructure.
**To configure your monitor's infrastructure**
1. Sign in to the **AWS Management Console** to start the Welcome to Deadline Cloud setup, then choose **Next**.
1. Enter the **Monitor name** — for example **AnyCompany Monitor**.
1. (Optional) To change the **Monitor URL**, choose **Edit URL**.
1. (Optional) To change the **AWS Region** so it's closest to your users, choose **Change Region**.
1. Select the Region closest to your users.
1. Choose **Apply Region**.
1. (Optional) To further customize your monitor setup, select **[Additional settings](#additional-monitor-settings)**.
1. If you are ready for [Step 2: Define farm details](define-the-farm.md), choose **Next**.
### Additional settings
Deadline Cloud setup includes additional settings. With these settings, you can view all the changes Deadline Cloud setup makes to your AWS account, configure your monitor user role, and change your encryption key type.
#### AWS IAM Identity Center
AWS IAM Identity Center is a cloud-based single sign-on service for managing users and groups. IAM Identity Center can also be integrated with your enterprise single sign-on (SSO) provider so that users can sign in with their company account.
Deadline Cloud enables IAM Identity Center by default, and it is required to set up and use Deadline Cloud. By default, the IAM Identity Center instance that you use for Deadline Cloud must be in the same AWS Region as the monitor. However, if you have Multi-Region support enabled in IAM Identity Center, you can create a monitor in a different Region. For more information, see [What is AWS IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html).
#### Configure service access role
An AWS service can assume a service role to perform actions on your behalf. Deadline Cloud requires a monitor user role for it to give users access to resources in your monitor.
You can attach AWS Identity and Access Management (IAM) managed policies to the monitor user role. The policies give users permissions to perform certain actions, such as creating jobs in a specific Deadline Cloud application. Because applications depend on specific conditions in the managed policy, if you don’t use the managed policies, the application might not perform as expected.
You can change the monitor user role after you complete setup, at any time. For more information about user roles, see [IAM Roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id.html#id_iam-roles).
The following tabs contain instructions for two different use cases. To create and use a new service role, choose the **New service role** tab. To use an existing service role, choose the **Existing service role** tab.
------
#### [ New service role ]
**To create and use a new service role**
1. Select **Create and use a new service role**.
1. (Optional) Enter a **Service user role** name.
1. Choose **View permission details** for more information about the role.
------
#### [ Existing service role ]
**To use an existing service role**
1. Select **Use an existing service role**.
1. Open the dropdown list to choose an existing service role.
1. (Optional) Choose **View in IAM console** for more information about the role.
------
# Step 2: Define farm details
Back on the Deadline Cloud console, complete the following steps to define the farm details.
1. In **Farm details**, add a **Name** for the farm.
1. For **Description**, enter the farm description. A description can help you identify your farm's purpose.
1. Create a group and add uses for your farm. After you set up your farm, you can use the Deadline Cloud management console to add or change groups and users.
1. (Optional) Choose **Additional farm settings**.
1. (Optional) By default, your data is encrypted with a key that AWS owns and manages for your security. You can choose **Customize encryption settings (advanced)** to use an existing key or to create a new one that you manage.
If you choose to customize encryption settings using the checkbox, enter a AWS KMS ARN, or create a new AWS KMS by choosing **Create new KMS key**.
1. (Optional) Choose **Add new tag** to add one or more tags to your farm.
1. Choose one of the following options:
+ Select **Skip to Review and Create** to [ review and create your farm](review-and-create.md).
+ Select **Next** to proceed to additional, optional steps.
# (Optional) Step 3: Define queue details
The queue is responsible for tracking progress and scheduling work for your jobs.
1. Starting in **Queue details, **provide a **Name** for the queue.
1. For **Description**, enter the queue description. A clear description can help you quickly identify your queue's purpose.
1. For **Job attachments**, you can either create a new Amazon S3 bucket or choose an existing Amazon S3 bucket. If you don't have an existing Amazon S3 bucket, you'll need to create one.
1. To create a new Amazon S3 bucket, select **Create new job bucket**. You can define the name of the job bucket in the **Root prefix** field. We recommend calling the bucket **deadlinecloud-job-attachments-[QUEUENAME]**.
You can only use lowercase letters and dashes. No spaces or special characters.
1. To search for and select an existing Amazon S3 bucket, select **Choose from existing Amazon S3 bucket**. Then, search for an existing bucket by choosing **Browse S3**. When the list of your available Amazon S3 buckets display, select the Amazon S3 bucket you want to use for your queue.
1. (Optional) Choose **Additional farm settings**.
1. If you are using customer-managed fleets, select **Enable association with customer-managed fleets**.
1. For customer-managed fleets, add a **Queue-configured user**, and then set the POSIX and/or Windows credentials. Alternatively, you can bypass the run-as functionality by selecting the checkbox.
1. If you want to set a budget for a queue, choose **Require a budget for this queue**. If you require a budget, you must create the budget using the Deadline Cloud console to schedule jobs in the queue.
1. Your queue requires permission to access Amazon S3 on your behalf. We recommend you create a new service role for every queue.
1. For a new role, complete the following steps.
1. Select **Create and use a new service role**.
1. Enter a **Role name** for your queue role or use the provided role name.
1. (Optional) Add a queue role **Description**.
1. You can view the IAM permissions for the queue role by choosing **View permission details**.
1. Alternatively, you can select an existing service role.
1. (Optional) Add environment variables for the queue environment using name and value pairs.
1. (Optional) Add tags for the queue using key and value pairs.
Choose one of the following options:
+ Select **Skip to Review and Create** to [ review and create your farm](review-and-create.md).
+ Select **Next** to proceed to additional, optional steps.
# (Optional) Step 4: Define fleet details
A fleet allocates workers to execute your rendering tasks. If you need a fleet for your rendering tasks, check the box for **Create fleet**.
1. **Fleet details**
1. Provide both a **Name** and optional **Description** for your fleet.
1. Review the fleet type and operating system for awareness.
1. In the **Instance market type** section, choose either **Spot**, **On-demand**, or **Wait and Save Instance**. Amazon EC2 On-demand instances provide faster availability and Amazon EC2 Spot and Wait and Save instances are better for cost saving efforts.
1. For **Auto scaling** the number of instances in your fleet, choose both a **Minimum** number of instances and a **Maximum** number of instances.
We strongly recommend to always set the minimum number of instances to **0** to avoid incurring extra costs.
1. Review the worker capabilities for awareness.
1. (optional) Choose **Additional fleet settings**
1. Your fleet requires permission to write to CloudWatch on your behalf. We recommend you create a new service role for every fleet.
1. For a new role, complete the following steps.
1. Select **Create and use a new service role**.
1. Enter a **Role name** for your fleet role or use the provided role name.
1. (Optional) Add a fleet role **Description**.
1. To view the IAM permissions for the fleet role, choose **View permission details**.
1. Alternatively, you can use an existing service role.
1. (Optional) Add tags for the fleet using key and value pairs.
After you enter all the fleet details, choose **Next**.
# Step 5: Review and create
Review the information entered to create your farm. When you're ready, choose **Create farm**.
The progress of your farm's creation is displayed on the **Farms** page. A success message displays when your farm is ready for use.
# Set up your workstation
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.
**Note**
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.
We provide reasonable defaults for keeping workstations secure. For more information about securing your workstation, see [Security best practices - workstations](https://docs.aws.amazon.com/deadline-cloud/latest/userguide/security-best-practices.html#workstations).
**Topics**
+ [Step 1: Install the Deadline Cloud submitter](#submitter-installation)
+ [Step 2: Install and set up Deadline Cloud monitor](#install-deadline-cloud-monitor)
+ [Step 3: Launch the Deadline Cloud submitter](#load-dca-plugin)
## Step 1: Install the Deadline Cloud submitter
The following sections guide you through the steps to install the Deadline Cloud submitter.
**Note**
**Unreal Engine:** The Unreal Engine submitter is not included in the standard installer and requires a separate setup process. For installation instructions, see the [Unreal Engine Submitter Setup Guide](https://aws-deadline.github.io/unreal-engine/setup-submitter/).
### Download the submitter installer
Before you can install the Deadline Cloud submitter, you must download the submitter installer.
1. Download the submitter installer for your operating system:
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/deadline-cloud/latest/userguide/submitter.html)
1. (Optional) [Verify the authenticity of downloaded software](security-best-practices.md#verify-installer).
### Install the Deadline Cloud submitter
With the installer, you can install the following submitters:
| Software | Supported versions | Windows installer | Linux installer | MacOS (arm64) installer |
| --- | --- | --- | --- | --- |
| [Adobe After Effects](adobe-after-effects.md) | 2024 - 2026 | Included | Not included | Included |
| [Autodesk 3ds Max](autodesk-3ds-max.md) | 2024 - 2026 | Included | Not included | Not included |
| [Autodesk Arnold for Cinema 4D](maxon-cinema-4d.md) | 4.8.4.1 | Included | Not included | Included |
| [Autodesk Arnold for Maya](autodesk-maya.md) | 7.1 - 7.4 | Included | Included | Included |
| [Autodesk Maya](autodesk-maya.md) | 2023 - 2026 | Included | Included | Included |
| [Autodesk VRED](autodesk-vred.md) | 2025 - 2026 | Included | Not included | Not included |
| [Blender](blender.md) | 3.6 - 5.0 | Included | Included | Included |
| [Chaos V-Ray for Maya](autodesk-maya.md) | 6 - 7 | Included | Included | Included |
| [Foundry Nuke](foundry-nuke.md) | 15 - 17 | Included | Included | Included |
| [KeyShot Studio](keyshot.md) | 2023 - 2025 | Included | Not included | Included |
| [Maxon Cinema 4D](maxon-cinema-4d.md) | 2024 - 2026 | Included | Not included | Included |
| [Maxon Redshift for Maya](autodesk-maya.md) | 2025-2026 | Included | Included | Included |
| [SideFX Houdini](sidefx-houdini.md) | 19.5 - 21.0 | Included | Included | Included |
**Note**
**Unreal Engine:** The Unreal Engine submitter is not included in the standard installer and requires a separate setup process. For installation instructions, see the [Unreal Engine Submitter Setup Guide](https://aws-deadline.github.io/unreal-engine/setup-submitter/).
------
#### [ Windows ]
1. In a file browser, navigate to the folder where the installer downloaded, and then select `DeadlineCloudSubmitter-windows-x64-installer.exe`.
1. If a **Windows protected your PC** pop-up displays, choose **More info**.
1. Choose **Run anyway**.
1. After the AWS Deadline Cloud Submitter Setup Wizard opens, choose **Next**.
1. 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:
1. Right-click on **DeadlineCloudSubmitter-windows-x64-installer.exe**, and then choose **Run as administrator**.
1. Enter your administrator credentials, and then choose **Yes**.
1. Choose **System** for the installation scope.
1. After selecting the installation scope, choose **Next**.
1. Choose **Next** again to accept the installation directory.
1. Select **Integrated submitter for Nuke**, or whichever submitter you want to install.
1. Choose **Next**.
1. Review the installation, and choose **Next**.
1. Choose **Next** again, and then choose **Finish**.
------
#### [ Linux ]
**Note**
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.
1. Open a terminal window.
1. To do a system install of the installer, enter the command **sudo -i** and press **Enter** to become root.
1. Navigate to the location where you downloaded the installer.
For example, **cd /home/*USER*/Downloads**.
1. To make the installer executable, enter **chmod \$1x DeadlineCloudSubmitter-linux-x64-installer.run**.
1. To run the Deadline Cloud submitter installer, enter **./DeadlineCloudSubmitter-linux-x64-installer.run**.
1. When the installer opens, follow the prompts on your screen to complete the Setup Wizard.
------
#### [ macOS (arm64) ]
1. In a file browser, navigate to the folder where the installer downloaded, and then select the file.
1. After the AWS Deadline Cloud Submitter Setup Wizard opens, choose **Next**.
1. Choose **Next** again to accept the installation directory.
1. Select **Integrated submitter for Maya**, or whichever submitter you want to install.
1. Choose **Next**.
1. Review the installation, and choose **Next**.
1. Choose **Next** again, and then choose **Finish**.
------
## Step 2: Install and set up Deadline Cloud monitor
You can install the Deadline Cloud monitor desktop application with Windows, Linux, or macOS.
------
#### [ Windows ]
1. Download the Deadline Cloud monitor installer for Windows:
[Download Deadline Cloud monitor for Windows](https://downloads.deadlinecloud.amazonaws.com/dcm/latest/DeadlineCloudMonitor_x64-setup.exe)
1. Run the downloaded installer and follow the prompts to complete the installation.
To perform a silent install, use the following command:
```
DeadlineCloudMonitor_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_x64-setup.exe /S /D={InstallDirectory}
```
------
#### [ Linux (AppImage) ]
**To install Deadline Cloud monitor AppImage on Debian distros**
1. Download the Deadline Cloud monitor AppImage:
[Download Deadline Cloud monitor (AppImage)](https://downloads.deadlinecloud.amazonaws.com/dcm/latest/deadline-cloud-monitor_amd64.AppImage)
1.
**Note**
This step is for Ubuntu 22 and up. For other versions of Ubuntu, skip this step.
To install libfuse2, enter:
```
sudo apt update
sudo apt install libfuse2
```
1. To make the AppImage executable, enter:
```
chmod a+x deadline-cloud-monitor_amd64.AppImage
```
------
#### [ Linux (Debian) ]
**To install Deadline Cloud monitor Debian package on Debian distros**
1. Download the Deadline Cloud monitor Debian package:
[Download Deadline Cloud monitor (.deb)](https://downloads.deadlinecloud.amazonaws.com/dcm/latest/deadline-cloud-monitor_amd64.deb)
1.
**Note**
This step is for Ubuntu 22 and up. For other versions of Ubuntu, skip this step.
To install libssl1.1, enter:
```
wget https://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
```
1. To install the Deadline Cloud monitor Debian package, enter:
```
sudo apt update
sudo apt install ./deadline-cloud-monitor_amd64.deb
```
1. 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**
**Note**
Rocky Linux 9 and Alma Linux 9 use OpenSSL 3.0 by default and don't include the `libssl.so.1.1` library. You must install the `compat-openssl11` package for Deadline Cloud monitor to run.
1. Download the Deadline Cloud monitor RPM:
[Download Deadline Cloud monitor (.rpm)](https://downloads.deadlinecloud.amazonaws.com/dcm/latest/deadline-cloud-monitor.x86_64.rpm)
1. Add the extra packages for the Enterprise Linux 9 repository:
```
sudo dnf install epel-release
```
1. Install `compat-openssl11` for the `libssl.so.1.1` dependency:
```
sudo dnf install compat-openssl11 deadline-cloud-monitor.x86_64.rpm
```
**To install Deadline Cloud monitor RPM on Red Hat Linux 9**
**Note**
Red Hat Linux 9 uses OpenSSL 3.0 by default and doesn't include the `libssl.so.1.1` library. You must install the `compat-openssl11` package for Deadline Cloud monitor to run.
1. Download the Deadline Cloud monitor RPM:
[Download Deadline Cloud monitor (.rpm)](https://downloads.deadlinecloud.amazonaws.com/dcm/latest/deadline-cloud-monitor.x86_64.rpm)
1. Enable the CodeReady Linux Builder repository:
```
subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms
```
1. Install the extra packages for Enterprise RPM:
```
sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
```
1. Install `compat-openssl11` for the `libssl.so.1.1` dependency:
```
sudo dnf install compat-openssl11 deadline-cloud-monitor.x86_64.rpm
```
**To install Deadline Cloud monitor RPM on Rocky Linux 8, Alma Linux 8, or Red Hat Linux 8**
1. Download the Deadline Cloud monitor RPM:
[Download Deadline Cloud monitor (.rpm)](https://downloads.deadlinecloud.amazonaws.com/dcm/latest/deadline-cloud-monitor.x86_64.rpm)
1. Install the Deadline Cloud monitor:
```
sudo dnf install deadline-cloud-monitor.x86_64.rpm
```
------
#### [ macOS (arm64) ]
1. Download the Deadline Cloud monitor installer for macOS:
[Download Deadline Cloud monitor for macOS (arm64)](https://downloads.deadlinecloud.amazonaws.com/dcm/latest/Deadline Cloud Monitor aarch64.dmg)
1. Open the downloaded file. When the window displays, select and drag the Deadline Cloud monitor icon into the **Applications** folder.
------
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 the authenticity of downloaded software](security-best-practices.md#verify-installer) 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**
1. Open **Deadline Cloud monitor**.
1. When prompted to create a new profile, complete the following steps.
1. Enter your monitor URL into the URL input, which looks like **https://*`MY-MONITOR`*.deadlinecloud.amazonaws.com/**
1. Enter a **Profile** name.
1. Choose **Create Profile**.
Your profile is created and your credentials are now shared with any software that uses the profile name that you created.
1. 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:
1. Delete the profile. In the left navigation pane, choose **Deadline Cloud monitor** > **Settings** > **Delete**.
1. Create a new profile with the changes that you want.
1. From the left navigation pane, use the **>Deadline Cloud monitor** option to do the following:
+ Change the Deadline Cloud monitor profile to log in to a different monitor.
+ Enable **Autologin** so you don’t have to enter your monitor URL on subsequent opens of Deadline Cloud monitor.
1. Close the Deadline Cloud monitor window. It continues to run in the background and enable other Deadline Cloud tools to access your render farm.
1. For each digital content creation (DCC) application that you plan to use for your rendering projects, complete the following steps:
1. From your Deadline Cloud submitter, open the Deadline Cloud workstation configuration.
1. 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 similar steps.
**To launch the Deadline Cloud submitter in Blender**
**Note**
Support for Blender is provided using the conda environment for service-managed fleets. For more information, see [Default conda queue environment](create-queue-environment.md#conda-queue-environment).
1. Open **Blender**.
1. In the **Render** menu, choose **Submit to AWS Deadline Cloud**.
1. If you are prompted to install GUI dependencies, choose **OK** and the Deadline Cloud submitter dialog will appear shortly.
1. If you are not already authenticated in the Deadline Cloud submitter, the **Credentials Status** shows as **NEEDS\$1LOGIN**.
1. Choose **Login**. You will be prompted to log in with your user credentials in a browser.
1. You are now logged in and the **Credentials Status** shows as **AUTHENTICATED**.
1. Choose **Submit**.
Now your job is submitted to your Deadline Cloud farm and will be processed by a compatible fleet. For information on how to view job progress in the monitor, see [Using the Monitor](https://docs.aws.amazon.com/deadline-cloud/latest/userguide/working-with-deadline-monitor.html).