Other Services Accounts
Learn how to onboard, monitor, and manage Other Services accounts in CoreStack including 12 supported tools and Custom Tools, with summary cards and quick actions.
Feature Overview
Other Services Accounts is a section within CoreStack's Governance module that enables FinOps Practitioners and Platform Engineers to onboard, monitor, and manage third-party service provider accounts across two categories — Other Tools (12 supported tools) and Custom Tools (user-defined integrations). The dashboard provides interactive summary cards surfacing key account health metrics at a glance.
This feature covers Datadog, Splunk, CircleCI, Elastic, Microsoft Teams, Salesforce Sales Cloud, Dropbox, Okta, New Relic, Dynatrace, Grafana, IBM Tencent, and any custom tool. It does not cover AI Services or Data Services accounts.
How It Works
When a user navigates to the Other Services page, summary cards load at the top — one per supported tool type for Other Tools, and one aggregated card for Custom Tools. Each card shows four health metrics and quick-action links. Clicking a card filters the account table to that tool type.
Onboarding follows a three-step wizard (Prerequisites → Basic Details → Storage Access) for all standard Other Tools. Custom Tool onboarding includes one additional step — Custom Tool Details — between Prerequisites and Basic Details, where users define the tool name, description, and logo.
Prerequisites
Before using the Other Services Accounts section, ensure the following are in place:
-
Access: You have the required permissions in CoreStack to access Governance > Account Governance.
-
Accounts onboarded: At least one account must be onboarded for a tool type to show non-zero counts on its summary card.
-
Valid credentials: Account credentials should be valid and active. Accounts with invalid credentials appear in the Fix It count.
-
Cloud account configured: A cloud account must be onboarded in CoreStack with a configured storage bucket for the Storage Access step.
Onboarding an Other Services Account
Navigate to Governance > Account Governance > Other Services.
Click Onboard Other Services in the top right corner. On the Onboard Other Services page, two sections appear:
- Custom Tools — onboard any external provider such as SaaS, AI, data providers, PaaS, or private cloud services.
- Collaboration Tools — select from 12 pre-configured tools. For example: Datadog for monitoring cost reports, Splunk for logging and analytics costs, CircleCI for CI/CD pipeline expenses, and Dropbox for storage costs.
Click Onboard under the chosen tool to enter the onboarding wizard.
Step 1: Prerequisites
Confirm FinOps is selected under Select Product(s). Only FinOps-related products are applicable for Other Services integrations.
Click Next to proceed.
Step 2: Custom Tool Details
This step is unique to Custom Tool onboarding. It allows you to define the tool before configuring account details. Collaboration Tools skip this step entirely and proceed directly from Step 1 (Prerequisites) to Step 2 (Basic Details).
Note: This step only appears when onboarding a Custom Tool. It does not appear for standard Collaboration Tools.
In the Custom Tool Details step, enter the following:
-
Tool Name: Enter a name for the custom tool.
-
Tool Description (optional): Enter a description of the tool.
-
Logo: Upload a logo image. Supported formats: JPG, JPEG, PNG. Maximum file size: 5MB.
Click Next to proceed.
Step 3: 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.
Click Next to proceed.
Step 4: Storage Access
In the Storage Access step, configure how CoreStack accesses billing data for this account. This step uses AWS storage configuration, as billing data is stored in an Amazon S3 bucket.
Under Storage Configuration, choose how CoreStack should access the storage for this account.
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 fill in the following fields:
-
Cloud Account: Select the cloud account from the dropdown. Only active cloud accounts onboarded in CoreStack appear here. If no active accounts are available, the message "No active Cloud Accounts found" is shown.
-
Storage Bucket: Select the S3 bucket where billing data is stored.
-
File Path: Enter the path within the bucket where the billing files are located.
Click Save & Validate to verify the configuration before proceeding.
Option 2: Use a Cloud Account Not Onboarded with Product
If the storage bucket belongs to an AWS account that is not onboarded in CoreStack, leave the Cloud Account Onboarded with Product checkbox unselected. You will need to provide AWS credentials directly. Select the authentication method under AWS Configuration:
Option 2a: Assume Role
Uses IAM-based temporary credentials for secure, short-lived access to AWS resources. In the Assume Role Credentials section, enter the following:
-
Role ARN: The Amazon Resource Name of the IAM role CoreStack will assume to access the bucket.
-
External ID: A unique identifier used to prevent confused deputy attacks. This must match the External ID configured in the IAM trust policy for the role.
-
MFA Enabled: Select True or False depending on whether MFA is required by the IAM role's trust policy.
-
Storage Bucket: Enter the name of the S3 bucket where billing data is stored.
-
File Path: Enter the path within the bucket where the billing files are located.
Click Save & Validate to verify the configuration before proceeding.
Option 2b: Access Key
Uses static, long-term AWS credentials. In the Access Key Credentials section, enter the following:
-
Access Key: The AWS access key ID for the IAM user or service account.
-
Secret Key: The corresponding secret access key for the IAM user or service account.
-
Storage Bucket: Enter the name of the S3 bucket where billing data is stored.
-
File Path: Enter the path within the bucket where the billing files are located.
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.
Other Services Dashboard
Navigate to Governance > Account Governance > Other Services.
Other Tools
The Other Services page displays one summary card per supported tool. The 12 supported tools are: Datadog, Splunk, CircleCI, Elastic, Microsoft Teams, Salesforce Sales Cloud, Dropbox, Okta, New Relic, Dynatrace, Grafana, and IBM Tencent.
Each card shows:
-
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 filter the account table below to that tool type.
Custom Tools
One aggregated summary card covers all user-defined custom tool accounts, showing aggregate counts. Click the Custom Tools card to filter the table to show all custom tool accounts.
Quick Actions
Each summary card includes up to three quick-action links:
| Quick Action | When Active | What It Does? |
|---|---|---|
| Fix It | Invalid credential count > 0 | Navigates directly to the account with invalid credentials |
| Reactivate | Inactive account count > 0 | Navigates to the first inactive account for that provider |
| View | Active account count > 0 | Filters the table to show only active and governed accounts |
Note: When the count for a quick action is zero, the link is greyed out and cannot be clicked.
Managing Other Services Accounts
After onboarding, click the ⋯ (actions menu) in the Actions column for any account row:
-
View: Opens the Other SaaS Service Account Summary page.
-
Edit: Opens the account for editing — update name, description, or storage configuration.
-
Deactivate: Suspends the account without deleting it.
-
Delete: Permanently removes the account from CoreStack.
View Account Details
Click View to open the Other SaaS Service Account Summary page.
The Details tab shows Basic Details (Account Name, Tool Name, Currency) and Storage Access (Cloud Account, Storage Bucket, File Path, Credential Status).
Click the FinOps tab to review the Cost Processing status — confirming 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.
Warning: Deleting an Other Services account permanently removes it and all associated data from CoreStack. This action cannot be undone.
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 of the Other Services page to export the full account list. The exported file contains all account details visible in the table.
Frequently Asked Questions
Q: What is the difference between Other Tools and Custom Tools?
Other Tools are pre-configured integrations for 12 supported providers. Custom Tools allow you to onboard any external provider not on the supported list by defining the tool name, description, and logo.
Q: What is the extra Custom Tool Details step?
When onboarding a Custom Tool, an additional Custom Tool Details step appears between Prerequisites and Basic Details. This is where you define the tool name, description, and upload a logo. It does not appear for standard Collaboration Tools.
Q: Why is the Fix It link greyed out?
The Fix It link is only active when the Accounts with Invalid Credentials count is greater than zero. When all credentials are valid, the link is greyed out.
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: My storage configuration has changed — how do I update it?
Click the ⋯ actions menu for the relevant account and select Edit. Update the details in the Storage Access step and click Finish to save.
Q: What is shown on the FinOps tab?
The FinOps tab shows 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.
Note: If the issue persists, contact CoreStack support with the tool name and the error message displayed.
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.