Create a filter to show untagged resources in Lucidscale

​@jday Do you want to create a filter that shows all resources but does not display their tags or do you want to create a filter that shows all untagged resources?

If the former, here’s a thread about filtering resources: https://community.lucid.co/product-questions-3/filtering-resources-5194 and here’s a blog post about customizing your view: https://www.lucidchart.com/blog/cloud-architecture-custom-views.

If the latter, The Tag Editor in AWS's web console allows you to search for "All resource types" where a specific tag is not present. For example, you can list everything that is missing the tag "environment". Or you could use the special case filter “tag:none -tag.key:aws*”

You might want to consider implementing automated tagging policies to reduce the number of untagged resources. For example, you could use this: github.com/llizamab/aws-tags-monitorization or https://github.com/aws-samples/aws-organizations-tag-inventory. It will take you to a link outside of Lucid.

I hope that helps!

Trying to create a filter that shows all untagged resources. 

We are doing some cleanup and creating diagrams based on the applications still in some older accounts that need to be migrated. We are trying to create diagrams for these apps to help the teams understand what is left.

Hi ​@jday, thank you for your post and Aparrish for assisting here! To confirm, are you hoping to filter the untagged resources in an existing generated model? Or create a new import with all untagged resources?

This will help us better understand your use-case and share more information. Thanks! 

I am hoping to create a filter that displays the untagged resources in an existing model.

If I need to create a new model to do this that is fine as well. 

Also, just to be clear. I am not talking about resources that cannot be tagged.

If I have an EC2 instance that a team forgot to tag, I want to have that displayed. 

The diagrams are for cleaning up older accounts before we set up tagging policies. See if we can find any dependencies between the resources.