Cannot see 'Databricks Lakehouse Platform" on prod AWS Cost Explorer
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2023 10:52 AM
Hi,
Currently, we have two different AWS accounts: dev and prod. We also have two different workspaces: one for dev and another for prod. The strange thing is that prod costs are being added to the dev account on AWS Cost Explorer ("Databricks Lakehouse Platform" service). I don't see any "Databricks Lakehouse Platform" costs on prod.
Can someone explain how Databricks connects and reports costs to AWS? Is it a Databricks config issue?
Thanks.
Labels:
- Labels:
-
AWS
-
Billing and Cost Management
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2023 02:10 PM
Databricks uses tags and AWS CloudTrail logs to connect and report costs to AWS.
Tags can be used to monitor costs and attribute Databricks usage to different business units and teams.
AWS CloudTrail logs can be used to calculate the exact cost of API requests for a Databricks file system (DBFS) S3 bucket.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2023 04:17 AM
Yes. However, I think AWS Cost Explorer is still powerful because you can compare Databricks against all the other services. Why am I seeing prod and dev aggregated on dev?
![](/skins/images/97567C72181EBE789E1F0FD869E4C89B/responsive_peak/images/icon_anonymous_message.png)
![](/skins/images/97567C72181EBE789E1F0FD869E4C89B/responsive_peak/images/icon_anonymous_message.png)