1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
What resources are you creating via CloudFormation? I did the same ("aws cloudformation create-change-set") with a simple template that has an S3 bucket resource. After "execute-change-set", the tags were propagated to the S3 bucket. However, I believe this propagation does not happen to all resources. Either it's not supported yet or it's a bug. Same case if you create/update CloudFormation stacks via the console.
I saw a similar open issue in github regarding this: CloudFormation Resource Tag Propogation.
If I need my resources to be properly tagged, I explicitly define the Tags property to the resources in the CFN template.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 mois
Thank you for you answer.
The services I created were a Glue Crawler and a Glue DB.
I will test it with other services but it's strange that for some services does it and for other don't.
I agree, if I need specific tags for the service I use the Tags property in the CF template as well, but because I want to apply a set of "standard" tags for all the resources I was thinking on doing it this way.
Thank you, Jorge.