If you’re familiar with Deadline 10 and looking to start using AWS Portal, we recommend starting here.

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.

AWS Portal Infrastructure Fails To Start

What Went Wrong

The AWS Portal Infrastructure is failing to start and is displaying the DELETE_FAILED status.

Figuring Out What Went Wrong

  1. Open the AWS Management Console.

  2. Go to Services > CloudFormation

  3. Click the Main Infrastructure stack. This will be the one with just the Stack Name and no region after it.

  4. Open the Events tab at the bottom of the screen.

  5. Look for the CREATE_FAILED event.

  6. The Status Reason column in the row with the CREATE_FAILED event will have the reason why your Infrastructure failed to create.

Solutions

VPC Limit Reached

You will get this Status Reason if you have reached your maximum number of VPCs for the region your in. You will either need to delete the other VPCs or request to have your limit increased.

API: s3:PutBucketTagging Access Denied

If you are using Deadline 10.1.7 or earlier we recommend updating to benefit from managed policies. If you can’t update please make sure your IAM policy is up to date.