- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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. :)
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?
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
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.