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.
Submit
you cant launch more than 20 instances in a region
0
0
The provided answer is correct, please read the AWS documentation details below;
Elastic Load Balancing supports three types of load balancers: Application Load Balancers, Network Load Balancers, and Classic Load Balancers.
Resource Default Limit
Load balancers per region 20 †
† This limit includes both your Application Load Balancers and your Classic Load Balancers. This limit can be increased upon request.
1
0
So, “A” is correct and not to mentioned, “D” doesn’t make sense
1
0
Answer is D
0
1
Answer is D
The reason is the instances which are used for development and test should be Reserved Instance. So as for the reserved instance, there is a limitation for per Availability, refer link as below.
http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html
20 Reserved Instances per Availability Zone, per month, plus 20 regional Reserved Instances.
View link below for more information
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-reserved-instances.html#ri-limits
You are limited to purchasing 20 Reserved Instances per Availability Zone, per month, plus 20 regional Reserved Instances. Therefore, in a region that has three Availability Zones, you can purchase 80 Reserved Instances in total: 20 per Availability Zone (60) plus 20 regional Reserved Instances.
0
1
The question stated “The CloudFormation template is trying to launch ***60 new EC2 instances in a single AZ.***’
The soft limit is 20 EC2 per AZ.
0
0
Q: How do I run systems in the Amazon EC2 environment?
Once you have set up your account and select or create your AMIs, you are ready to boot your instance. You can start your AMI on any number of On-Demand instances by using the RunInstances API call. You simply need to indicate how many instances you wish to launch. If you wish to run more than 20 On-Demand instances, complete the Amazon EC2 instance request form.
https://aws.amazon.com/ec2/faqs/
0
0
http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html#limits_ec2
Amazon Elastic Compute Cloud (Amazon EC2) Limits
On-Demand Instances Limits vary depending on instance type. For more information, see How many instances can I run in Amazon EC2.
Spot Instances Limits vary depending on instance type, region, and account. For more information, see Spot Instance Limits.
Reserved Instances 20 Reserved Instances per Availability Zone, per month, plus 20 regional Reserved Instances. For more information, see Reserved Instance Limits.
0
0