-
Notifications
You must be signed in to change notification settings - Fork 54
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
AWS::EC2::instance (specify TagSpecification in EBS BlockDeviceMapping) #133
Comments
@PatMyron @luiseduardocolon i saw you folks referenced this issue on the master issue #228 , any chance you have an update on this ? Asking as this lack of functionality does really impact myself and others in sorting out the EBS tagging which is a must to not waste the $$ down the pipe. Moved to ASG with LT and while
|
We also take care of EBS tagging in userdata section, and it would be nice to take care of it on CloudFormation level. Looking forward to this CloudFormation update. |
This has been "coming soon" for 3 full months now, is there an ETA for when this will be available? |
Any updates on this issue yet? |
I'm following up on this - if you don't hear from me in a couple of weeks, ping me again here :) |
@luiseduardocolon as requested :) |
@luiseduardocolon any progress? |
Soon 1 year this issue has been opened... |
Hi @luiseduardocolon 👋 ... any updates? |
Hi @luiseduardocolon Could you please provide us some update on this issue? |
Any updates here? We want to be able to use cloud formation and specify both the instance and volume tags just like in the screenshot below. In my organization there will be some policies applied for having tags on these resources, and we will be blocked if we cannot do this since our automation is depending on cloud formation at the moment. |
@luiseduardocolon My team has been using CloudFormation templates to create AWS::EC2::Instances (along with EIPs, NetworkInterfaces, SecurityGroups, EIPAssociations, etc). The security/IT division of my company is implementing a new requirement that volumes be tagged upon on creation. Therefore, the common StackOverflow workaround of updating tags in the UserData block within the CF template will not work for us, since we expect volume creation will be blocked by this new policy. We need the ability to specify tags for the default root /dev/sda1 volume before the EC2 instance is created. Is there some way to do this, via LaunchTemplates or otherwise? |
FYI for anyone who has this issue, I was in fact able to tag volumes on creation using LaunchTemplates. You can define a LaunchTemplate in the CloudFormation template file, and reference it from an Instance also defined by the same CloudFormation, if you need the LaunchTemplate to have some parameterized dynamic values. Or you can do as I did, and make one static LaunchTemplate manually, outside the scope of the CloudFormation, and reference it within the Instance's JSON/YAML. |
Really wanting this. The inability to easily add tags to BlockDeviceMappings makes it harder to create a tag-based DLM Lifecycle Policy. |
I was really hoping this would get released by ReInvent 2020. |
This is beyond unprofessional. Hundreds of CFN updates have been released since this issue moved to "coming soon" 10 full months ago, most of them not on the public roadmap, some of them involving EC2/EBS as recently as last week. What's the point of this roadmap when our submitted issues are disrespected even more than the service itself? |
While there is no valid ETA on this feature (which I feel is very crucial or desired) but, this is doable like this: UserData: But, this is NOT a recommended solution. I prefer to use something native provided by AWS CF rather implementing some hack. |
Any update on this from CF? |
|
Can we at least hope this will arrive by AWS ReInvent 2021? :) |
Hmmm... How did this go from "Coming soon" to "Researching"? |
Just one more comment for visibility, ran into this missing feature today. Would like to see this implemented. |
Hoping for resolution (or any update at this point) by re:invent 2022 😢 |
A new property is added to EC2::Instance https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html#cfn-ec2-instance-propagatetagstovolumeoncreation to propagate on creation |
Wait a sec… this just got shipped!?! Excellent news!!!!🎉 🎉 🎉 No more user data script workarounds. 😊 Thanks for the great news. |
That is helpful information, nice that we can propagate tags now. But it doesn't meet the demands of this ticket, which is to allow custom tags on the EBS volumes during launch. Doesn't seem this feature is anywhere in sight, as it's been moved all the way back to Researching. |
aws-cloudformation/cloudformation-coverage-roadmap#133 just shipped. Docs: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html#cfn-ec2-instance-propagatetagstovolumeoncreation Waiting on cloudfromation specs to get bumped to the latest version. Depends on #17844. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
aws-cloudformation/cloudformation-coverage-roadmap#133 just shipped. Docs: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html#cfn-ec2-instance-propagatetagstovolumeoncreation Waiting on cloudfromation specs to get bumped to the latest version. Depends on aws#17844. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Instructions for CloudFormation Coverage New Issues Template
Quick Sample Summary:
The text was updated successfully, but these errors were encountered: