Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Cloud Intelligence Dashboards tag filtering for resources

0

Hello,

I'm trying to create a Cudos or CID dashboard that calculates data/costs for just a specific keyword in name of an item e.g. oracle. Each of our CFN stacks have the tag of Name populated. Having shared the tag from payer accounts to the account with the CUR data, it shows up in the CUR table as resource_tags_user_name. I've tried filtering on it, I've tried adding a control based on the "resource_name" and filtering on the parameter (which is the alias in the summary view for it), but while it does correctly find all related items, the cost of said items is very low vs what I know to be the actual cost (e.g. $1.2k a month vs what is more like $20k a month). Now, all of these volumes are provisioned as ec2 volumes, not strictly EBS volumes, but either way the cost is WAY off.

Is Name not a reliable tag? Is there a billing attribute that I'm missing? I've basically used various EC2 and EBS graphs as templates to simply add the filter on and the result is the same. Kinda stumped here.

Thanks very much in advance.

Topics
AnalyticsCloud Financial ManagementStorage
Tags
Cloud Intelligence DashboardsAmazon Quick SightAmazon Elastic Block StoreAWS Billing
Language
English

asked 4 years ago1.7K views

2 Answers
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

AWS
EXPERT

answered 4 years ago

  • rePost-User-1981166
    4 years 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?

0

"Name" is a user tag, but is different from the "name" tag, which is also a user tag. Make sure that you are using and have activated the "Name" tag as a cost allocation tag. That tag is what is shown as "resource_tags_user_name" in the Athena table and what you need to map to a field in your QuickSight dataset.

If you have both "Name" and "name" in use, you can activate both tags, but I would recommend creating a cost category to harmonize them both to a single "Name" cost category and using that. Cost categories appear as cost_category_* in Athena.

AWS
EXPERT

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content