AWS driver not tagging EBS volumes

[vmattos]

trafficstars

The option --amazonec2-tags doesn't seem to tag the EBS volumes, and it seems there is no other option the explicitly tag them, according to this doc https://docs.docker.com/machine/drivers/aws/

Is there any way to tag the volumes during the creation?

[dhohengassner]

also missing this feature 👍

[vmattos]

We have an auto-termination policy in our company for everything that is not tagged So being able to tag resources other than the instances themselves is a must 😞

[lestephane]

This seems to be a general problem with the aws driver, the security group that gets created is also not tagged. Maybe change the summary of this issue to something more generic like "AWS driver does not tag all resources it creates (EBS, Security Group...)"

[webmozart]

Same here - I'd like to tag the root volume so that its cost can be monitored in the cost explorer

[webmozart]

I just did some research on whether this is feasible and want to record my findings. Maybe someone has the Go skills to do this (I don't) - it seems easy - or I'll find some time to try my luck at this eventually. :)

In amazonec2.go line 748, we receive the created Instance object after finishing the spot request or running the instance directly.

That Instance should contain a list of InstanceBlockDeviceMappings, which should each contain an EbsInstanceBlockDevice, which store the volumeId of the volume.

If we record these volume IDs and then pass them along as Resources in the call to CreateTags(), this should be solved.

[hatim-heffoudhi]

same here, +1 for this feature 👍