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

Autoscaling for EC2 Spot Fleet #9817

Closed
ghost opened this issue Aug 19, 2019 · 3 comments
Closed

Autoscaling for EC2 Spot Fleet #9817

ghost opened this issue Aug 19, 2019 · 3 comments
Labels
service/ec2 Issues and PRs that pertain to the ec2 service.

Comments

@ghost
Copy link

ghost commented Aug 19, 2019

This issue was originally opened by @hdryx as hashicorp/terraform#22510. It was migrated here as a result of the provider split. The original body of the issue is below.


Hi,

Just start converting what i did in console to Terraform for my Spot Fleet. I used aws_spot_fleet_request resource, and all works as expected.

However i can't find how to configure the autoscaling for that Spot Fleet ?

In AWS console we can find that functionnality and i want to know if is there a way to do it in Terraform ?

Current Terraform Version

0.12.6

@ghost ghost added the service/ec2 Issues and PRs that pertain to the ec2 service. label Aug 19, 2019
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Aug 19, 2019
@ewbankkit
Copy link
Contributor

@hdryx I think the mixed_instances_policy attribute of the aws_autoscaling_group resource should provide the functionality you need.

@github-actions
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Aug 11, 2021
@breathingdust breathingdust removed the needs-triage Waiting for first response or review from a maintainer. label Sep 17, 2021
@github-actions github-actions bot removed the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Oct 14, 2021
@github-actions
Copy link

github-actions bot commented Jun 2, 2022

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

No branches or pull requests

2 participants