If you’re new to AWS Portal we recommend starting here. If you’re new to Deadline we recommend starting here.

Switching AWS Accounts

Before Switching Accounts

Before you switch to a different AWS account, it is strongly recommended that you stop all spot fleets and infrastructures. If you do not do this, the spot fleets and infrastructures will continue to run in your old account and charges will apply.

Creating A New S3 Bucket

After signing into the new account you will need to create a new S3 bucket in the new account. It is recommended that if the old account is no longer going to be used for AWS Portal that you delete the S3 bucket that was used for the AWS Portal asset transfer system. If you do not do this, charges may apply for the storage used by this bucket. To do this:

  1. Log into the AWS Console under the old account.

  2. Expand the “All services” section and under “Storage” click the “S3” link.

  3. Select the bucket that was used by the asset transfer system from the list.

  4. Click “Delete Bucket”.

  5. If the bucket is not empty, you will be prompted to type the name of the bucket before you can delete it.

    ../_images/delete-bucket.png

  6. Press confirm.

To create a new bucket in the new AWS account you will need to click the “New Bucket” button in the AWS Portal Settings dialog.

../_images/create-bucket.png

Once the bucket has been created, if the Asset Server is currently running, you will need to restart the Asset Server. On Windows, you can do this by opening Task Manager (press Ctrl + Shift + Esc), going to the “Services” tab, right clicking on “AWSPortalAssetServer” and selecting “Restart”.

../_images/windows-services.png

On linux this can be done by running the command sudo service awsportalassetservershellscript restart. Note that restarting the service must be done on the machine the Asset Server is running on. If the Asset Server is not currently installed or you intend to reinstall it, you will need to create the new bucket before you run install the Asset Server, or run the “Remove Orphaned AWS Entities” procedure as explained in the next section.

Manually Stopping Infrastructure and Spot Fleets

Cleaning Up The Database

If for whatever reason you no longer have access to the old AWS Account and need to remove Spot Fleets or infrastructures associated with this account from the Deadline Database, you can do this by opening the AWS Portal Settings dialog and clicking on the “Advanced” tab and pressing the “Remove Orphaned AWS Entities” button.

../_images/cleanup-aws-orphans.png

You will be prompted to type in your AWS Account Id to confirm that you wish to do this before proceeding. This will remove any spot fleets, infrastructures, and S3 buckets not owned by the account you are currently signed in from the Deadline database. It will not stop or delete these entities in AWS itself. If any spot fleets, infrastructures, or S3 buckets are not deleted from the old AWS account charges will apply.

Stopping Spot Fleets

From the AWS console:

  1. Switch your region to the region that your spot fleet was created in by clicking the region drop down in the upper right-hand corner and selecting the correct region.

    ../_images/switch-region.png

  2. Expand the “All services” section and under “Compute” click on “EC2”.

  3. In the left side-bar, click on “Spot Requests”.

  4. Select the spot fleet you wish to stop.

  5. Click the “Actions” button and then “Cancel Spot Request”.

    ../_images/cancel-spot-request.png

Stopping Infrastructures

From the AWS console:

  1. Switch your region to the region that your infrastructure was created in by clicking the region drop down in the upper right-hand corner and selecting the correct region.

    ../_images/switch-region.png

  2. Ensure that you have stopped all spot fleet requests associated with the infrastructure (see previous section).

  3. Expand the “All services” section and under “Management Tools” click on “CloudFormation”

  4. Select the “Stack” associated with the infrastructure you wish to remove.

  5. Click on the “Resources” tab and click the link in the “Physical ID” column in the row where “ClientBucket” is the “Logical ID”.

    ../_images/cloudformation-bucket.png

  6. Select the “certs” directory (and any other directories that may be in the bucket)

  7. Under the “More” drop-down select “Delete”

    ../_images/delete-certs.png

  8. Close the “S3 Management Console” tab to get back to the CloudFormation console.

  9. Ensure the stack for the infrastructure you wish to delete is still selected then click the “Actions” button and “Delete Stack”

    ../_images/delete-stack.png

  10. Press the “Yes, Delete” button and wait for the stack to finish deleting.