You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should have terraform that's good enough to be able to work around these errors
Error: creating EC2 Instance: InsufficientInstanceCapacity: We currently do not have sufficient m5.xlarge capacity in the Availability Zone you requested (us-east-1a). Our system will be working on provisioning additional capacity. You can currently get m5.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1b, us-east-1c, us-east-1d, us-east-1f.
With the error above, the Terraform isn't specifying an AZ
Use Case
Intermittently, these errors cause our pipelines to fail in anywhere this module is used (mostly in us-east-1 and in this repo )
Impact
Waste of time and money due to inability to merge branches due to failing pipeline
Completion
I see a few options here:
Move this to an Autoscaling group of 1, that way we can utilize mixed instance policies. (this might cost extra $$$ depending on the instance that gets provisioned)
Don't use us-east-1
Use aws_ec2_capacity_reservation (this costs extra $$$)
Additional Context
The text was updated successfully, but these errors were encountered:
zack-is-cool
changed the title
Resolve issue with being unable to provision instances due to resource limitations
Insufficient $instance capacity in Az
Jul 21, 2023
Persona
DU IaC Admin
Description
We should have terraform that's good enough to be able to work around these errors
With the error above, the Terraform isn't specifying an AZ
Use Case
Intermittently, these errors cause our pipelines to fail in anywhere this module is used (mostly in us-east-1 and in this repo )
Impact
Waste of time and money due to inability to merge branches due to failing pipeline
Completion
I see a few options here:
aws_ec2_capacity_reservation
(this costs extra $$$)Additional Context
The text was updated successfully, but these errors were encountered: