Skip to main content

AWS Deadline Cloud for Maya

User guide | Service documentation | Deadline Cloud on GitHub

pypi python license

AWS Deadline Cloud for Maya is a Python package that supports creating and running Autodesk Maya jobs within AWS Deadline Cloud. It provides both the implementation of a Maya plug-in for your workstation that helps you offload the computation for your rendering workloads to AWS Deadline Cloud to free up your workstation's compute for other tasks, and the implementation of a command-line adaptor application based on the Open Job Description (OpenJD) Adaptor Runtime that improves AWS Deadline Cloud's ability to run Maya efficiently on your render farm.

Compatibility

This library requires:

  1. Maya 2024 - 2027,
  2. MtoA 5.3.5 or higher,
  3. Python 3.9 or higher; and
  4. Linux, Windows, or a macOS operating system.

Plugin support: Arnold for Maya 2024-2027; VRay and Redshift for Maya 2025-2027.

Maya 2027 requires the deadline-cloud-v2 conda channel; the deadline-cloud channel does not support Maya 2027. The submitter plug-in uses it when submitting directly, but exported job bundles carry no channel, so point the queue environment at it instead.

Redshift's Maya 2027 support ships inside its 2026 version line, so use the maya-redshift 2026 conda package with Maya 2027; there is no 2027 package.

Versioning

This package's version follows Semantic Versioning 2.0, but is still considered to be in its initial development, thus backwards incompatible versions are denoted by minor version bumps. To help illustrate how versions will increment during this initial development stage, they are described below:

  1. The MAJOR version is currently 0, indicating initial development.
  2. The MINOR version is currently incremented when backwards incompatible changes are introduced to the public API.
  3. The PATCH version is currently incremented when bug fixes or backwards compatible changes are introduced to the public API.

Getting Started

This Maya integration for AWS Deadline Cloud has two components that you will need to install:

  1. The Maya submitter plug-in must be installed on the workstation that you will use to submit jobs; and
  2. The Maya adaptor must be installed on all of your AWS Deadline Cloud worker hosts that will be running the Maya jobs that you submit.

Before submitting any large, complex, or otherwise compute-heavy Maya render jobs to your farm using the submitter and adaptor that you set up, we strongly recommend that you construct a simple test scene that can be rendered quickly and submit renders of that scene to your farm to ensure that your setup is correctly functioning.

Maya Submitter Plug-in

The Maya submitter plug-in creates a shelf button in your Maya UI that can be used to submit jobs to AWS Deadline Cloud. Clicking this button reveals a UI to create a job submission for AWS Deadline Cloud using the AWS Deadline Cloud client library. It automatically determines the files required based on the loaded scene, allows the user to specify render options, builds an Open Job Description template that defines the workflow, and submits the job to the farm and queue of your choosing.

To install the submitter plug-in:

  1. Install the deadline-cloud-for-maya Python package, with mayapy, into the Maya installation on your workstation by following Maya's official online documentation (e.g. For Maya 2024).
  2. Copy the contents of the /maya_submitter_plugin directory from the release branch of deadline-cloud-for-maya GitHub repository into a directory in Maya's module search paths. See the MAYA_MODULE_PATH section of Maya's official documentation (e.g. For Maya 2024) for a list of the default search paths on your system.
  3. Within Maya, enable the DeadlineCloudForMaya plug-in in Maya's Plug-in Manager. (Main menu bar: Windows -> Settings/Preferences -> Plug-in Manager)
  4. To supply AWS account credentials for the submitter to use when submitting a job you can either:
    1. Install and set up the Deadline Cloud Monitor, and then log in to the monitor. Logging in to the monitor will make AWS credentials available to the submitter, automatically.
    2. Set up an AWS credentials profile as you would for the AWS CLI, and select that profile for the submitter to use.
    3. Or default to your AWS EC2 instance profile credentials if you are running a workstation in the cloud.

Maya Adaptor

Jobs created by this submitter require this adaptor be installed on your worker hosts, and that both the installed adaptor and the Maya executable be available on the PATH of the user that will be running your jobs.

Or you can set the MAYAPY_EXECUTABLE to point to the Maya mayapy executable.

The adaptor application is a command-line Python-based application that enhances the functionality of Maya for running within a render farm like Deadline Cloud. Its primary purpose for existing is to add a "sticky rendering" functionality where a single process instance of Maya is able to load the scene file and then dynamically be instructed to perform desired renders without needing to close and re-launch Maya between them. It also has additional benefits such as support for path mapping, and reporting the progress of your render to Deadline Cloud. The alternative to "sticky rendering" is that Maya would need to be run separately for each render that is done, and close afterwards. Some scenes can take 10's of minutes just to load for rendering, so being able to keep the application open and loaded between renders can be a significant time-saving optimization; particularly when the render itself is quick.

If you are using the default Queue Environment, or an equivalent, to run your jobs, then the adaptor will be automatically made available to your job. Otherwise, you will need to install the adaptor.

The adaptor can be installed by the standard python packaging mechanisms:

$ pip install deadline-cloud-for-maya

After installation, test that it has been installed properly by running the following as the same user that runs your jobs and that maya can be run as the same user:

$ maya-openjd --help
$ maya -help

For more information on the commands the OpenJD adaptor runtime provides, see here.

Maya Adaptor by default will skip version checking when opening scene. If you want to change this, set the MAYA_IGNORE_VERSION enviroment variable accordingly.

For example, to enable version checking:

export MAYA_IGNORE_VERSION=false

Maya Software Availability in AWS Deadline Cloud Service Managed Fleets

You will need to ensure that the version of Maya that you want to run is available on the worker host when you are using AWS Deadline Cloud's Service Managed Fleets to run jobs; hosts do not have any rendering applications pre-installed. The standard way of accomplishing this is described in the service documentation. You can find a list of the versions of Maya that are available by default in the user guide if you are using the default Conda queue environment in your setup.

Viewing the Job Bundle that will be submitted

To submit a job, the submitter first generates a Job Bundle, and then uses functionality from the Deadline package to submit the Job Bundle to your render farm to run. If you would like to see the job that will be submitted to your farm, then you can use the "Export Bundle" button in the submitter to export the Job Bundle to a location of your choice. If you want to submit the job from the export, rather than through the submitter plug-in then you can use the Deadline Cloud application to submit that bundle to your farm.

Security

We take all security reports seriously. When we receive such reports, we will investigate and subsequently address any potential vulnerabilities as quickly as possible. If you discover a potential security issue in this project, please notify AWS/Amazon Security via our vulnerability reporting page or directly via email to AWS Security. Please do not create a public GitHub issue in this project.

Telemetry

See telemetry for more information.

License

This project is licensed under the Apache-2.0 License.

Release files for deadline-cloud-for-maya 0.15.21

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deadline-cloud-for-maya 0.15.21
File Size Uploaded
deadline_cloud_for_maya-0.15.21.tar.gz 64.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for deadline-cloud-for-maya 0.15.21
File Interpreter ABI Platform
deadline_cloud_for_maya-0.15.21-py3-none-any.whl Python 3 none any Details

Total release size: 148.3 kB

Release files / deadline_cloud_for_maya-0.15.21.tar.gz

Download URL deadline_cloud_for_maya-0.15.21.tar.gz
Size 64.7 kB
Tags Source
SHA-256 checksum
How to use checksums
4b24935ae0760ea1a02a8774eb03d864bdfa277a9f233474dd508416ce1176a6
BLAKE2b-256 checksum
How to use checksums
35f54232190fd4c5d15d039c97ee0a2cbf43c4c6f284c2a654f02aedf7f52b74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.

Transparency log

Release files / deadline_cloud_for_maya-0.15.21-py3-none-any.whl

Download URL deadline_cloud_for_maya-0.15.21-py3-none-any.whl
Size 83.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5d6f25f3d1a4ab80d480dd59898644f0557b890ed838286281808343a59e6878
BLAKE2b-256 checksum
How to use checksums
adce06d66af010cd2a00b5fdea01355fea562302f2144888c41ab1317f52716f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page