Documentation and Best Practices

Learn how to use Cloudability and get the most out of our cloud cost management tool

— User assistance content is no longer updated on this site —

— For up-to-date information, check out the Apptio Help Center


Why am I seeing "(not set)" in AWS Tag reports?

For the latest version of this help, see:

If you've built a report in Cloudability that includes a tag column then it's likely you've seen a row called "(not set)".

This could mean one of three things: 

  1. You have not told AWS to include all of your tags in your Cost Allocation file. See Section 2 of this help article for how to include AWS tags in cost allocation files.
  2. You have resources that are taggable but are not yet tagged. 
  3. You have AWS spending that is simply not taggable. Common examples are Support Costs, upfront Reserved Instance fees, Tax and EBS snapshots.

Due to #3, you'll likely have at least some "(not set)" in your account.  You can exclude it from your reports by adding a "not equals" filter for that tag with the value of "(not set)".  

See the example below on how to achieve this.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.