AMI Tags not propagated to other accounts?

[Byte Flinger]

I have built an AWS AMI image using the EBS backed builder and I set the "ami_users" to a couple of different accounts so the ami is available for using in all of these acounts.

I noticed that the AMI in the account which I built the image on has all the AMI tags I configured in the packer configuration however the other accounts have no tags whatsoever in that same ami.

Is anybody aware if this is by design or an issue with packer ebs backed builder?

Regards
Byte

[Rickard von Essen]

This is how AWS works. AMI's can be shared with other accounts, basically giving them read access. But tags are a separate construct, metadata separate from the resources they "tag". They are not shared and and not visible from the other account just because the AMI is shared.

The other account can add it's own tags to an AMI shared with it.

Hope that clears things up a bit. Feel free to follow up with further questions. 

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/521def5a-952a-424b-9576-ce44ef28f8d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Byte Flinger]

Thank you very much for the answer Rickard. It is too bad one cannot rely on that functionality but at least I am now aware of the issue.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt88%2BPZckxHCBBN09pic4geL0eD-aQn7VXX8sz-HdUotiQ%40mail.gmail.com.