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.

Connecting to the Infrastructure

If you would like to connect to the Gateway instance in the Infrastructure for troubleshooting purposes use the following steps depending on what operating system you are connecting from.

Every Operating System

The following instructions must be followed regardless of the operating system you are connecting from.

  • Get Public IP of Gateway Instance
    In the AWS Web Console Navigate to Services > EC2 > INSTANCES > Instances. Click the filter bar, Click Tag Keys > Name, type in Gateway (type in ReverseForwarder instead if you are using Deadline 10.0.13.6 or earlier). This will filter down to only show you the Gateway instance. Next copy down either the IPv4 Public IP or the Public DNS (IPv4).

../../_images/FindingGateway.png

  • Locate the private key
    You’ll need to use the DashKey to SSH into the Infrastructure instance. You can find the DashKey in the root folder of wherever you installed AWS Portal Link. If you installed AWS Portal Link on Windows the DashKey can be found in C:\Program Files (x86)\Thinkbox\AWSPortalLink\ by default. If you installed AWS Portal Link on Linux the DashKey can be found in /opt/Thinkbox/AWSPortalLink/ by default.

  • Get the default user name
    On the Gateway instance the default user is ec2-user.