Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insufficient $instance capacity in Az #35

Open
zack-is-cool opened this issue Jul 21, 2023 · 1 comment
Open

Insufficient $instance capacity in Az #35

zack-is-cool opened this issue Jul 21, 2023 · 1 comment
Assignees

Comments

@zack-is-cool
Copy link
Member

zack-is-cool commented Jul 21, 2023

Persona

DU IaC Admin

Description

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:

  1. 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)
  2. Don't use us-east-1
  3. Use aws_ec2_capacity_reservation (this costs extra $$$)

Additional Context

@zack-is-cool 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
@zack-is-cool zack-is-cool self-assigned this Jul 21, 2023
@zack-is-cool
Copy link
Member Author

moving to next because we have a workaround for now - don't use us-east-1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant