The AWS Portal Server install fails with the following error message:
Failed to setup AWS Portal Server with S3. Please check the log for more information.
Example of the above text as it shows in the installer.
There can be various causes to this error. Access the installation log to locate the cause. Checkout the AWS Portal Installer Failed documentation for log locations and possible resolutions.
Possible causes are listed below:
AWS Account Activation Incomplete: AWS Portal will fail to install if billing and account activation is not complete. Here are some possible errors that could indicate your account has not been activated:
Error: An unexpected error occurred while setting up AWS Portal: Got Access Denied when trying to PutBucket in S3 Bucket aws-porta;-cache-*. Please make sure your user has the 'iam:GetUser' IAM Permission to make these error messages better. Please make sure your IAM user <unknown> has the following IAM Permission(s) to access S3 Bucket. s3:PutBucket
Try accessing S3 or launching an EC2 instance from the AWS Management Console. If the account is not activated, you will be presented with an error or warning.
AWS Portal IAM Users: The IAM Policy assigned to the IAM User whose security credentials were used for installation is out of date or incorrect. Make sure that the your Admin and AWS Portal IAM Policy is the most updated version. If you have not performed the setup of the IAM Policy steps, follow Creating an Admin IAM User and Creating an AWSPortal IAM User.
Failed to Get Public IP Address: The deadlinecommand call that sets up the AWSPortal cannot determine the public IP and crashes. The error will look something like below:
Error running C:\Program Files\Thinkbox\Deadline10\bin/DeadlineCommand.exe RunAWSPortalS3Setup ap-northeast-1: Program ended with an error exit code
[18:31:29] Please enter your AWS Access Key ID:
Please enter your AWS Secret Access Key:
Error: Failed to get public IP address. (Deadline.AWS.AWSPortalSetupException)
Program ended with an error exit code
Make sure that http://checkip.amazonaws.com is accessible via the AWS Portal machine so that the installer can obtain the public ip address. Alternatively the public IP override can be set during the installation to workaround this issue.
AWS Endpoints: AWS endpoints could be blocked outbound your network. Allow the following endpoints outbound from the machine running AWS Portal. Allow the following endpoints outbound from the machine running AWS Portal.
AWS Portal Setup Cannot be Completed While an Infrastructure is Running: This can be caused by someone shutting down an infrastructure from the console instead of through Deadline. The Deadline repository will still believe there is a infrastructure running and will refuse to install AWS Portal. To resolve it, stop any infrastructures you are running. If you are not running one follow here to remove orphaned entries.