Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

🚀 25% OFF All Practice Exams, Video Courses, & eBooks – Cyber Sale Extension!

Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified Solutions Architect Associate EC2 instances limit

  • giadasalvatori

    Member
    November 27, 2024 at 6:36 pm

    Hi,

    Could you clarify this question for me?

    based on what was I supposed to understand that the problem was the vCPU limit and not the limit on the number of instances?

    Regards

    Giada

  • Neil-TutorialsDojo

    Member
    November 28, 2024 at 9:57 am

    Hello Giada,

    Good day!

    Yes, you are right—the issue in the question is related to the vCPU limit.

    As of 2019, AWS moved to vCPU-based limits for On-Demand EC2 instances. These limits are applied at the regional. See https://aws.amazon.com/ec2/faqs/#How_many_instances_can_I_run_in_Amazon_EC2

    The failure after 20 instances suggests that the total number of vCPUs required by the instances exceeded the region’s vCPU limit. This limit is often more restrictive, especially when launching many instances of high-performance instance types, which consume more vCPUs. As a result, the vCPU limit is more likely the cause of the failure, not the number of instances.

    Hence, the correct answer is: There is a vCPU-based On-Demand Instance limit per region, which is why subsequent requests failed. The solution is to submit a limit increase request to AWS, and once it’s approved, you can retry the failed requests.

    Based on the snippet, your answer is “Select a different Availability Zone and retry the failed request. Simply choosing another Availability Zone might not resolve the issue if the vCPU limit is still being exceeded. Therefore, requesting a limit increase for vCPUs is the more appropriate solution.

    I hope this helps.

    Regards,

    Neil @ Tutorials Dojo

Viewing 1 - 2 of 2 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now
Skip to content