I agree AWS should tag all resources with their names already for them to show up in the Cost Explorer. However, we already tag by cost center or teams to identify costs. It's required as a policy and baked in most of our automations. It's also a best practice recommended by even most basic tutorials. If you have a TAM, they would tell you to do this as well when your finance team or person is asking about why these bills are large.

Also, even if they are untagged, it's not like we need to tag them by hand, AWS Resource Tagging API works nice enough, and not every resource is costly that we need to tag them by resource-level.

I support what you are doing however there are too many companies working CUR data in S3 and none of them is good enough and neccessarily faster or more useful than Cost Explorer. Just wanted to understand what you can add on top of it, apart from automatic tagging? part.