-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Volumes created with aws_launch_configuration have no tags #1788
Comments
I am interested in this functionality as well. |
Hi folks! The autoscaling group APIs have not historically supported volume tagging until very recently when EC2 Launch Templates were announced at re:invent (provider issue: #2505). Launch templates are supported by both EC2 instances and autoscaling groups and contain support for volume tagging. It looks like this might be the way forward for supporting this feature on autoscaling group instances. Hope this helps. |
I would like this too |
I also need this 👍 |
Helpful feature, would be nice to have it |
i would like this as well :) |
+1 |
3 similar comments
+1 |
+1 |
+1 |
To tag any EC2 resources created implicitly via the launch template you can use the |
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! |
Terraform Version
Terraform v0.10.4
Instances created with "aws_instance" may include a "volume_tags" parameter when specifying root_block_device and/or ebs_block_device.
This option is missing from the aws_launch_config resource.
Therefore, volumes created for autoscaling group instances - Have No Tags -
This makes orphan volumes difficult to ID.
The text was updated successfully, but these errors were encountered: