After some research you discover that the problem is;

Your company has decided to set up a new AWS account for test and dev purposes. They already use AWS for
production, but would like a new account dedicated for test and dev so as to not accidentally break the
production environment. You launch an exact replica of your production environment using a CloudFormation
template that your company uses in production. However CloudFormation fails. You use the exact same
CloudFormation template in production, so the failure is something to do with your new AWS account. The
CloudFormation template is trying to launch 60 new EC2 instances in a single AZ. After some research you
discover that the problem is;

A.
For all new AWS accounts there is a soft limit of 20 EC2 instances per region. You should submit the limit
increase form and retry the template after your limit has been increased.

B.
For all new AWS accounts there is a soft limit of 20 EC2 instances per availability zone. You should submit
the limit increase form and retry the template after your limit has been increased.

C.
You cannot launch more than 20 instances in your default VPC, instead reconfigure the CloudFormation
template to provision the instances in a custom VPC.

D.
Your CloudFormation template is configured to use the parent account and not the new account. Change
the account number in the CloudFormation template and relaunch the template.