-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Support for AWS Auto Scaling EMR Clusters #713
Comments
+1 |
1 similar comment
+1 |
+1 |
8 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
I'm picking this up |
Opened a PR for this: #2877 |
Thanks to @darrenhaken, an |
Super. Thanks a lot @darrenhaken. Really cool feature. 🥇 |
Thanks you @darrenhaken, can't wait to use this feature in my next |
This has been released in version 1.10.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
This issue was originally opened by @lattwood as hashicorp/terraform#13913. It was migrated here as part of the provider split. The original body of the issue is below.
Hi there,
It would be great to have support for the new EMR Auto Scaling feature, ideally including support for EBS volumes, and possibly spot market bids. This would of course also require the ability to configure and manage the auto-scaling policy rules (scale out/in, min/max instances).
#11126 was closed after adding the feature required to setup Autoscaling Instance Groups in the AWS Console in hashicorp/terraform#12823 (don't want to encourage one foot in terraform land, the other in manual)
Affected Resource(s)
References
Auto Scaling for EMR Clusters
https://aws.amazon.com/blogs/aws/new-auto-scaling-for-emr-clusters/
The text was updated successfully, but these errors were encountered: