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
I would like to fire EC2 instances based on instance requirements rather than having to specify a given instance type. For example, I want a bare minimum of 4 vCPU with 16 GiBs of RAM across my EC2 instance fleet.
Expected Behavior
I don't mind if we implemented it in a non-backwards compatible way. Although, I believe it's doable. THe instance_requirements variable would clash if configured alongside the instance_type
Describe Ideal Solution
The TF provider has support for all of these elements:
Have a question? Please checkout our Slack Community or visit our Slack Archive.
Describe the Feature (Use Case)
I would like to fire EC2 instances based on instance requirements rather than having to specify a given instance type. For example, I want a bare minimum of 4 vCPU with 16 GiBs of RAM across my EC2 instance fleet.
Expected Behavior
I don't mind if we implemented it in a non-backwards compatible way. Although, I believe it's doable. THe instance_requirements variable would clash if configured alongside the instance_type
Describe Ideal Solution
The TF provider has support for all of these elements:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/launch_template#instance-requirements
In fact, the OSS Terraform-modules equivalent leverages a similar approach
https://github.com/terraform-aws-modules/terraform-aws-autoscaling/blob/master/main.tf#L160
Alternatives Considered
Stop using this module to create ASGs and rely on other partners or a self-baked one.
Additional Context
N/A
The text was updated successfully, but these errors were encountered: