Set up Domino FinOps

Learn how to set up Domino FinOps to empower organizations to optimize the performance of their AI projects while managing their cloud expenditures.

Configure cloud billing integration

Domino can integrate with cloud provider billing APIs so you can be confident that the costs you see in Domino represent your actual cloud bills.

To get detailed, usage-based cost allocations, Domino automatically tags all infrastructure usage with key metadata to associate the costs with your Domino Projects, organizations, users and Billing Tags.

There are 3 options for configuring FinOps cloud integration:

Fully automated cloud integration (AWS-only): Domino automatically provisions a cost usage report -and- configures the cloud billing integration.
Bring your own cost usage report (AWS-only): You provide a pre-provisioned cost usage report with Athena. Domino configures cloud billing integration.
Manual cloud integration: You must manually provision all the necessary resources and configure cloud billing integration yourself.

Fully automated cloud integration

Domino can fully automate cloud billing integration for AWS users who install Domino using the Domino terraform-aws-eks module.

Under the hood, Domino creates a cost usage report with Amazon Athena and configures FinOps to consume the cost usage report to display cost usage information to you.

To fully automate cloud integration: During installation, set the deploy manifest variable cost_analyzer.cloud_billing.enabled to true. Reach out to your Domino representative for more information about this method.

Pre-provisioned cost usage report

For customers who want to use their cost usage report outside of Domino, or for those who already have a pre-existing Athena cost usage report, you can bring your own Athena cost usage report to Domino.

In your domino.yml configuration file, update the cost_reporting fields with your cost usage report details:

cost_reporting:
  cloud_billing:
    aws:
      aws_account_id: _CHANGE_ME_
      athena_bucket_name: _CHANGE_ME_
      athena_region: _CHANGE_ME_
      athena_database: _CHANGE_ME_
      athena_table: _CHANGE_ME_
      athena_workgroup: _CHANGE_ME_

Manual cloud integration

Non-AWS users can manually provision their cost usage report and set up FinOps cloud integration using the documentation below.

To retrieve billing information from your cloud provider, contact your Domino representative to setup FinOps Cloud Billing Integration.

Configure long-term FinOps storage

Domino FinOps allows you to retain your cost data in blob storage for long-term analysis. To get a FinOps Enterprise license, contact your Domino representative.

There are 3 options to configure the long-term storage:

Fully automated federated storage: Domino provisions your S3 bucket and sets up federated storage.
Bring your own blob store: You provide a pre-provisioned S3 blog storage. Domino sets up federated storage.
Manual provisioning and federated storage: You must manually provision a blob store and set up federated storage.

Fully automated federated storage

AWS users can have Domino fully automate long-term storage. Domino can provision S3 buckets and set up federated storage at installation.

During installation, set the deploy manifest variable s3_costs_enabled to true. Reach out to your Domino representative for more information about this method.

Important

Domino provisions the S3 blob storage <deployer-id>-cost does not have a lifecycle by default. To store your data for a short period, update the blob storage lifecycle to the desired expiration configuration.

Pre-provisioned blob storage

Domino can set up federated storage for AWS users with an existing S3 blob store.

In your domino.yaml configuration file, update the cost_reporting fields with your S3 details:

cost_reporting:
  storage:
    s3:
      region: _CHANGE_ME_
      bucket: _CHANGE_ME_
      sse_kms_key_id: _CHANGE_ME_

Manual federated storage

Non-AWS users can manually provision their blob store and set up FinOps federated storage.

In your Domino cluster, create a new file called federated-store.yaml.
Format the contents of the file according to each cloud provider’s specifications.

Add a secret using federated-store.yaml:

kubectl create secret generic <secret_name> -n <namespace> --from-file=federated-store.yaml

Set .Values.kubecostModel.federatedStorageConfigSecret to the Kubernetes secret name.

Enable budgets and alerts

To enable budgets and alerts:

Go to Admin > Advanced > Feature Flags.
Enable the feature flag ShortLived.EnableCostBudgetsAndAlerts.
Enable the feature flag ShortLived.EnableBillingTags to allow aggregation of cost centers by Billing Tags.

Deploy default cost-reporting dashboard

You have the option to deploy a provided Domino App, enabling the creation of a cost-reporting dashboard. This dashboard offers a comprehensive view and detailed breakdown of various expenses you might incur.

To deploy the Domino App in your own Project, follow the instructions in the README from the Domino Cost App repository if you have the feature flag EnableBillingTags enabled, otherwise use the previously released version.

cost monitoring dashboard

Next steps

See how Domino FinOps can help you optimize cloud costs:

Automatically allocate usage-based costs to Projects, organizations, and users.
Proactively prevent overspending on compute and storage by setting budgets and sending alerts to team members approaching their limits.
Optimize Dataset storage usage to reduce cloud storage costs.
Generate chargeback/showback reports and use APIs to facilitate cost recovery across organizations and engage with high-expenditure users to optimize infrastructure usage.