How to use TAGS on aws_cost_usage ()

[maxx225566]

Is your feature request related to a problem? Please describe. The document (https://hub.steampipe.io/plugins/turbot/aws/tables/aws_cost_usage) mentions... dimension types (AZ , INSTANCE_TYPE, LEGAL_ENTITY_NAME, LINKED_ACCOUNT, OPERATION, PLATFORM, PURCHASE_TYPE, SERVICE, TAGS, ..... But I don't know how to enter the format of TAGS

Describe the solution you'd like I want to be able to support cost tags

Describe alternatives you've considered NO

Additional context

After I tried my best to enter any tags, the error displayed did not mention Definition dimension: TAGS

ex. select period_start, dimension_1 as account_id, dimension_2 as service_name, unblended_cost_amount :: numeric :: money from aws_cost_usage where granularity = 'MONTHLY' and dimension_type_1 = 'LINKED_ACCOUNT' and dimension_type_2 = 'TAGS'

Query 1: ERROR: rpc error: code = Unknown desc = operation error Cost Explorer: GetCostAndUsage, https response error StatusCode: 400, RequestID: 50018480-f3b3-4b8c-a85e-853a298180bb, api error ValidationException: Group Definition dimension is invalid. Valid values are AZ, INSTANCE_TYPE, LINKED_ACCOUNT, OPERATION, PURCHASE_TYPE, SERVICE, USAGE_TYPE, PLATFORM, TENANCY, RECORD_TYPE, LEGAL_ENTITY_NAME, INVOICING_ENTITY, DEPLOYMENT_OPTION, DATABASE_ENGINE, CACHE_ENGINE, INSTANCE_TYPE_FAMILY, REGION, BILLING_ENTITY, RESERVATION_ID, SAVINGS_PLANS_TYPE, SAVINGS_PLAN_ARN, OPERATING_SYSTEM

[misraved]

Hello @maxx225566, thanks for raising the feature request. I believe this is a potential question/issue in the AWS plugin.

Let me transfer it to the correct repository 👍 .

[misraved]

Hello @maxx225566, apologies for the delayed response.

After looking into the API which is being used in the background for this table, I figured out that we don't currently support Tags as an input.

The valid values of the DIMENSION column type include only the following parameters:

Valid values for the DIMENSION type are AZ, INSTANCE_TYPE, LEGAL_ENTITY_NAME, INVOICING_ENTITY, LINKED_ACCOUNT, OPERATION, PLATFORM, PURCHASE_TYPE, SERVICE, TENANCY, RECORD_TYPE, and USAGE_TYPE.

However, there is a scope for expanding the table to accept tag as a column input. I will look into the feasibility of adding this column 👍 .

The table document definitely needs an update to remove TAGS as an input parameter since it can be misleading. This will be fixed in the upcoming release 👍 .