Feature Overview

Data Services Accounts is a section within CoreStack's Governance module that enables FinOps Practitioners and Platform Engineers to onboard, monitor, and manage data service provider accounts — currently supporting Databricks and Snowflake. The Data Services dashboard provides interactive summary cards that surface key account health metrics at a glance, alongside a detailed account table for managing individual accounts.

This feature is most relevant when managing multiple data service accounts and needing to quickly assess their governance status, fix credential issues, or onboard new accounts. It is specific to data service providers and does not cover AI Services or Other Services accounts.

How It Works

When a user navigates to the Data Services page, interactive summary cards load at the top — one for Databricks and one for Snowflake. Each card displays four key health metrics: total account count, accounts with invalid credentials, inactive accounts, and active and governed accounts. Clicking a card highlights it and filters the account table below to show only accounts for that provider.

Prerequisites

Before using the Data Services Accounts section, ensure the following are in place:

• Access: You have the required permissions in CoreStack to access Governance > Account Governance.

• Data service accounts onboarded: At least one account must be onboarded for a provider to show non-zero counts. Cards for providers with no onboarded accounts display zero counts with an Onboard prompt.

• Valid credentials: Data service account credentials should be valid and active. Accounts with invalid credentials appear in the Fix It count on the relevant card.

• Cloud account configured: A cloud account must be onboarded in CoreStack with a configured storage bucket for billing data access during the Storage Access step.

Onboarding a Data Service Account

Navigate to Governance > Account Governance > Data Services.

Click Onboard Data Services in the top right corner. On the Onboard Data Services page, select the provider:

• Databricks — tracks big data costs and compute usage for Databricks workloads.

• Snowflake — imports billing data to track warehouse, query, and storage costs.

Click Onboard under the chosen provider to enter the onboarding wizard. The wizard has three steps.

Step 1: Prerequisites

In the Prerequisites step, confirm that FinOps is selected under Select Product(s). For data service integrations, only FinOps-related products are applicable for big data cost analysis and optimization.

Click Next to proceed.

Step 2: Basic Details

In the Basic Details step, enter the following:

• Account Name: Enter a name to identify this account within CoreStack.

• Description (optional): Enter a description for the account.

If you need to onboard multiple accounts at once, click Click here to download the CSV Template to download a bulk import template.

Click Next to proceed.

Step 3: Storage Access

In the Storage Access step, configure how CoreStack accesses billing data for this account.

Under Select Cloud Provider, choose AWS, Azure, GCP, or OCI to indicate where your billing data is stored. CoreStack renders the matching configuration panel below your selection.

AWS

Option 1: Use a Cloud Account Onboarded with Product

If your AWS storage bucket is already associated with a cloud account onboarded in CoreStack, select the Cloud Account Onboarded with Product checkbox, then select the Cloud Account, Storage Bucket, and File Path. Only active AWS cloud accounts onboarded in CoreStack appear in the dropdown; if none are available, CoreStack displays "No active Cloud Accounts found."

Click Save & Validate to verify the configuration before proceeding.

Option 2: Enter AWS Credentials Directly

If the storage bucket's AWS account is not onboarded in CoreStack, leave Cloud Account Onboarded with Product unselected and select an authentication method under AWS Configuration.

Option 2a

Assume Role: uses IAM-based temporary credentials. Enter the Role ARN, External ID, and whether MFA Enabled is True or False, along with the Storage Bucket and File Path.

Click Save & Validate to verify the configuration before proceeding.

Option 2b

Access Key: uses static, long-term credentials. Enter the Access Key, Secret Key, Storage Bucket, and File Path.

Click Save & Validate to verify the configuration before proceeding.

Azure

Option 1: Use a Cloud Account Onboarded with Product

If your Azure storage account is already associated with a cloud account onboarded in CoreStack, select the Cloud Account Onboarded with Product checkbox, then select the Cloud Account, Storage Account, Blob Container Name, and File Path. Only active Azure cloud accounts onboarded in CoreStack appear in the dropdown; if none are available, CoreStack displays "No active Cloud Accounts found."

Click Save & Validate to verify the configuration before proceeding.

Option 2: Enter Azure Application Credentials Directly

If the storage account's Azure subscription is not onboarded in CoreStack, leave Cloud Account Onboarded with Product unselected and enter your Azure Application Credentials under Azure Configuration

• Tenant ID
• Application ID
• Application Secret

Click List Subscriptions to continue.

Click Save & Validate to verify the configuration before proceeding.

GCP

Option 1: Use a Cloud Account Onboarded with Product

If your GCP storage bucket is already associated with a cloud account onboarded in CoreStack, select the Cloud Account Onboarded with Product checkbox, then select the Cloud Account, Storage Bucket, and File Path. Only active GCP cloud accounts onboarded in CoreStack appear in the dropdown; if none are available, CoreStack displays "No active Cloud Accounts found."

Click Save & Validate to verify the configuration before proceeding.

Option 2: Enter GCP Credentials Directly

If the storage bucket's GCP project is not onboarded in CoreStack, leave Cloud Account Onboarded with Product unselected and select an authentication protocol under Select Authentication Protocol.

Option 2a

Service Account (Recommended): enter the Project ID and upload a JSON credentials file using Upload Credentials File (JSON).

Enter the Storage Bucket and File Path, then click Save & Validate to verify the configuration before proceeding.

Option 2b

OAuth2: enter the Client ID, Client Secret, Redirect URI, and Authorization Code.

Enter the Storage Bucket and File Path, then click Save & Validate to verify the configuration before proceeding.

OCI

Option 1: Use a Cloud Account Onboarded with Product

If your OCI storage bucket is already associated with a cloud account onboarded in CoreStack, select the Cloud Account Onboarded with Product checkbox, then select the Cloud Account, Storage Bucket, and File Path. Only active OCI cloud accounts onboarded in CoreStack appear in the dropdown; if none are available, CoreStack displays "No active Cloud Accounts found."

Click Save & Validate to verify the configuration before proceeding.

Option 2: Enter Tenancy Credentials Directly

If the storage bucket's OCI tenancy is not onboarded in CoreStack, leave Cloud Account Onboarded with Product unselected and enter your Tenancy Credentials under OCI Configuration:

• User ID
• Fingerprint
• Tenancy ID
• Region
• Upload Credentials File (PEM)

Enter the Storage Bucket and File Path, then click Save & Validate to verify the configuration before proceeding.

Click Finish to complete onboarding. The newly onboarded account appears in the account table and the relevant summary card updates its counts.

Data Services Dashboard

Navigate to Governance > Account Governance > Data Services.

The Data Services page displays one summary card for Databricks and one for Snowflake. Each card shows:

• Total Accounts: The total number of onboarded accounts for that provider.

• Accounts with Invalid Credentials: Accounts with credential issues, with a Fix It action link.

• Deactivated Accounts: Inactive accounts, with a Reactivate action link.

• Active and Governed Accounts: Healthy, active accounts, with a View action link.

Click any card to highlight it and filter the account table below to show only accounts for that provider.

Quick Actions

Each summary card includes up to three quick-action links:

Managing Data Service Accounts

After onboarding, click the ⋯ (actions menu) in the Actions column for any account row:

• View: Opens the Data Service Account Summary page with full account details.

• Edit: Opens the account for editing — update the account name, description, or storage configuration.

• Deactivate: Suspends the account without deleting it.

• Delete: Permanently removes the account from CoreStack.

View Account Details

Click View from the actions menu to open the Data Service Account Summary page.

The Details tab shows:

• Basic Details: Account Name, Tool Name, and Currency.

• Storage Access: Cloud Account, Storage Bucket, File Path, and Credential Status.

Click the FinOps tab to review FinOps functionality. The Cost Processing status shows whether cost data is being actively collected and processed.

Edit

Click Edit from the actions menu to open the account for editing.

The Basic Details tab allows you to update the account name and description.

The Storage Access tab allows you to update the storage credentials. You can switch between authentication methods — Assume Role or Access Key — and modify the Role ARN, External ID, Storage Bucket, and File Path for Assume Role, or the Access Key, Secret Key, Storage Bucket, and File Path for Access Key. Click Finish to save your changes.

Deactivate

Click Deactivate from the actions menu to suspend the account without deleting it. A deactivated account stops collecting and processing cost data but retains all previously ingested data and configuration. The summary card for the relevant provider reflects the updated count under Deactivated Accounts. You can reactivate the account at any time using the Reactivate quick action on the summary card or from the actions menu.

Delete

Click Delete from the actions menu to permanently remove the account from CoreStack. Once deleted, the account no longer appears in the account table, all associated data is removed and cannot be recovered, and the summary card count for the relevant provider updates to reflect the removal. Use this option only when the account is no longer needed.

Filtering the Account Table

Use the ADD+ button above the account table to filter accounts. Available filter options:

• Credential Status — filter by Valid or Invalid credentials.

• SaaS Account Status — filter by account status (Active, Deactivated, etc.).

Exporting the Account List

Click the download icon in the top right to export the full account list. The exported file contains all account details visible in the table.

Frequently Asked Questions

Q: Why is the Fix It link greyed out on my card?

The Fix It link is only active when the invalid credentials count is greater than zero. When all credentials are valid, the link is greyed out.

Q: What happens when I click a summary card?

Clicking a card highlights it and instantly filters the account table to show only accounts for that data service provider. No full page reload occurs.

Q: A card shows zero accounts — what should I do?

No accounts have been onboarded for that provider yet. Click Onboard Data Services and follow the onboarding wizard to add the first account.

Q: My storage configuration has changed — how do I update it?

Click the ⋯ actions menu for the relevant account and select Edit. Update the Cloud Account, Storage Bucket, or File Path in the Storage Access step and click Finish to save.

Q: Can I onboard multiple accounts at once?

Yes. During the Basic Details step, click Click here to download the CSV Template to download a bulk import template.

Q: What is shown on the FinOps tab?

The FinOps tab shows the FinOps Functionality section with the Cost Processing status — confirming whether cost data is being actively collected and processed for the account.

Troubleshooting

Summary cards are not loading

Cause: The API failed to load account health data.

Solution:

• Check your network connection and refresh the page.

• If the cards display a loading error, click the Retry option on the card.

• If the issue persists, contact CoreStack support.

Storage validation fails during onboarding or edit

Cause: The selected cloud account does not have access to the specified storage bucket, or the file path is incorrect.

Solution:

• Confirm the cloud account has the required permissions to access the storage bucket.

• Verify the storage bucket exists and is accessible.

• Confirm the file path format is correct.

• Re-enter the details and click Save & Validate again.

Card counts do not reflect recent account changes

Cause: Card counts update on the scheduled data refresh cycle.

Solution:

• Wait for the next scheduled refresh cycle and reload the page.

• If counts appear stale for an extended period, contact CoreStack support with the provider name and expected count change.