By using AWS re:Post, you agree to the Terms of Use

Failed to create a node group for an EKS cluster: You've reached your quota for maximum Fleet Requests for this account

0

I tried to create an EKS cluster by terraform but the plan failed with the below error msg. [AsgInstanceLaunchFailures: You've reached your quota for maximum Fleet Requests for this account. Launching EC2 instance failed.]

I don't believe the root cause of this failure is a quota issue because there are not many EC2 instances within the region (ap-northeast-2). So I tried below to find what the real problem is but still on the same page. Please advise what I should do, thanks.

Fyr, the IAM user has administrator permission.

  • Run the same terraform code with the different account (all settings were same, only account (not IAM) was changed to my private one)
    • Result: Success to build
    • Conclusion: No issues with the code (network configuration is included)
  • Run the same terraform code in the different region (tried ap-east-1)
    • Result: Success to build
  • Changed an instance type from t3.medium to m4.large (the other settings were same)
    • Result: Failed to build with the same error
  • I am too getting the same error. I am using ap-southeast-2 region and instance_type=t3.xlarge.

  • Same error. It's new AWS account is new with very few EC2. Something else is wrong when done via TF automation or eksctl or manual. I need a solution to this.

    unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'. last error: 2 errors occurred: │ * eks-managed-ondemand-20220916000118777000000009-90c1a1cc-c40a-4d69-60fa-d40ad3479549: AsgInstanceLaunchFailures: You've reached your quota for maximum Fleet Requests for this account. Launching EC2 instance failed.

1 Answer
0

Hi. If you didn´t try to double-check your EC2 quota, I guess visiting https://console.aws.amazon.com/servicequotas/home will show you. Another thing to pay attention to if the node group that terraform wants to create is using the usual EC2 or Spot because the service quotas have specific values for each Spot EC2 family. Hope you find out the solution soon. :)

profile picture
answered a month ago
  • Hi, I checked the limit is 640 vCPUs and our account is using 18 vCPUs only in total so seems it's not limitation issue. In addition, the terraform code doesn't have any configuration about spot. When I've tried same code on the different region, usual EC2 instances were launched, not spot instances. Is there any other fact can cause the above error msg - You've reached your quota for maximum Fleet Requests for this account?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions