Hi @data_turtle, To find the AWS-associated costs from your Databricks SQL warehouse usage, you can tag clusters and pools, and these tags propagate both to detailed DBU usage reports and to AWS EC2 and AWS EBS instances for cost analysis.
However, if these tags are not showing up in AWS Cost Explorer, it may be due to some delay or issues in tag propagation. You can add tags when you edit the job to get specific job costs. These tags also propagate to job clusters created when a position is run, allowing you to use tags with your existing cluster monitoring. You can use the billable usage graphs in the account console to get the cost details, which can aggregate usage by individual tags. The billable usage CSV reports downloaded from the same page include default and custom tags.
For the AWS account a resource is in, you can use the cost tables as each resource has a cost attributed to it, and it contains the information to tell us which account it's in.
