Automated tagging solutions for difference types of resources?

Question

I am wondering if there is a solution out there for automating the tagging of resources. Specifically resources that have already have been created, I am not interested in updating those from console but rather dynamically with code. I am in the process of creating a (containerized) program that does this but wondering if there is an easier solution  I found this older blog post :https://aws.amazon.com/blogs/mt/auto-tag-aws-resources/. It is no longer supported but could work for my problem, however its looking like it may only support EC2 resources , while I need others to be tagged in addition.

Answer

This also provides an interesting solution: https://aws.plainenglish.io/how-to-auto-tag-new-aws-resources-and-deploy-solution-with-terraform-de48ec644d95

And this https://github.com/GorillaStack/auto-tag

Answer

Hello,

The available AWS Solution is that which you have already noted [here](https://aws.amazon.com/blogs/mt/auto-tag-aws-resources/). This solution uses CloudWatch to detect events from CloudTrail and invokes a Lambda function to tag the resources. As correctly stated, the solution example is for EC2 instances and associated EBS volumes. The solution can be customized where CloudWatch tracks more CloudTrail events and the Lambda code can be modified where necessary to tag the additional resources. Additionally, I noticed you mentioned this solution no longer works. Could you elaborate on this?

I dug further and found this article [here](https://carlospgarciat.medium.com/auto-tag-new-resources-in-aws-with-cloud-custodian-43d4f826264f) that talks about how to achieve this use-case using the [CloudCustodian](https://cloudcustodian.io/) tool.

Answer

Internally we have this artifact in APG for new AWS resources auto-tagging:

https://apg-library.amazonaws.com/content/b9e5beac-8c73-48f9-9964-b36094a5795a

Automated tagging solutions for difference types of resources?

Conteúdo relevante