1 Answer
- Newest
- Most votes
- Most comments
0
Name of ec2 instance as you see it in console is actually the tag "Name" So if your EC2 is named differently within the stack i would say it will affect Name tag. Probably better to use a tag other than Name
Relevant content
- asked 25 days ago
- asked 8 months ago
- asked a month ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 months ago
Thanks for the reply Iakov. It's actually the tag of Name that I want to filter on. While the resource in the stack is DBInstance or EBSDataVolume (which would be AWS::EC2::Instance and AWS::EC2::Volume respectively) the "Name" tag is explicitly set for both and indeed shows in the console as desired. I've added the alias in the summary view as "resource_name" to map to resource_tag_user_name that exists in the CUR table and when adding it as a Filter -> Filter List it does match the nearly 900 items that are there. If I select them that way or do a custom filter with includes "oracle" (without the quotes) the cost winds up being the same.
If I do not filter, the monthly cost in a few specific accounts is $44k, if I add the filter the cost drops to around $1.2k. I know based on the unit cost of $.08 per GB per month for gp3 volumes that the storage should be more than $20k for these accounts. I guess perhaps a better question to ask is is there some cost attribute/tag that I'm missing somehow that despite matching on the Name tag, without this attribute included in the list of filters the cost/usage is not being applied?