When using AWS Portal, creating an Infrastructure can fail for different reasons. The first step is to narrow down the cause of failure by either looking at the logs from Right click on Infrastructure → ‘View Infrastructure Information’ or from the Cloud Formation logs as described here. The ‘Status Reason’ for the event should have the reason why your Infrastructure failed to create.
Based on the reason for failure, you can follow the below resolution:
IAM Policy missing permissions to tag resources
As an example, you will see this in the status reason as
CREATE_FAILED API: s3:PutBucketTagging Access Denied'
If you are using Deadline 10.1.7 or earlier we recommend you upgrade to 10.1.8 so these policies can be managed for you. If you are unable to upgrade, you will need to update your IAM Policy attached to Deadline's AWSPortal IAM User to add the right permissions. This is because of the recent change in AWS Cloud Formation’s permission requirements that will take effect as of November 4, 2020.
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.