You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
AWS Cost Explorer has a resource filter that provides granularity of cost down to the resource level. When choosing a service such as S3 you can see the cost of specific buckets for instance. Currently there is not resource option for the dimensions
Describe the solution you'd like
Add ability to query resource level data from cost explorer, either in the cost explorer tables or in joined tables.
Describe alternatives you've considered
Downloading cost data as CSV and then using the CSV plugin, but the CSV plugin does not work with Pipes.
Additional context
Per resource granularity is not enabled by default, it must be enabled per service and most organizations do not do that due to the additional cost involved with collecting that data. Does SF have this enabled for all services or just select ones?
Is your feature request related to a problem? Please describe.
AWS Cost Explorer has a resource filter that provides granularity of cost down to the resource level. When choosing a service such as S3 you can see the cost of specific buckets for instance. Currently there is not resource option for the dimensions
Describe the solution you'd like
Add ability to query resource level data from cost explorer, either in the cost explorer tables or in joined tables.
Describe alternatives you've considered
Downloading cost data as CSV and then using the CSV plugin, but the CSV plugin does not work with Pipes.
Additional context
Per resource granularity is not enabled by default, it must be enabled per service and most organizations do not do that due to the additional cost involved with collecting that data. Does SF have this enabled for all services or just select ones?
https://turbot.zendesk.com/agent/tickets/7007
The text was updated successfully, but these errors were encountered: