Choose the hub workspace
The appliance deploys into one workspace, called the hub, and analyzes the whole account from there. Everything Lakemine creates lives in the hub. Nothing is deployed into your other workspaces, and they are still analyzed.
Installer, “Choose the hub workspace” panel. Workspace dropdown open listing the account’s workspaces, the region hint beneath it, and the “Sign in to this workspace” button.
Picking one
Pick a workspace that already has:
- Unity Catalog attached. The installer checks this and blocks if it is missing.
- A SQL warehouse. If it does not have one, the installer can create a small
serverless warehouse named
lakemine-whon the next step.
In practice this is usually a shared or platform workspace rather than a team’s development workspace. It needs to be somewhere that will still exist and still be administered in a year.
The installer runs two blocking checks once you pick one:
| Check | Blocking | What it means |
|---|---|---|
| Unity Catalog attached to this workspace | Yes | The workspace has a metastore, which the results schema and the system tables both depend on. |
| Signed in to this workspace | Yes | Workspace-level authentication succeeded. |
Sign in to the workspace
Select Sign in to this workspace. This is a second browser sign-in, at the workspace level rather than the account level. Databricks treats these as separate credentials, so both are needed.
Regional coverage
If any workspaces in your account sit outside the hub’s region, the installer tells you now, before you deploy.
system.billing is global, so cost coverage is account wide regardless of region.
The compute, query, and lakeflow telemetry is stored per region, so workspaces outside
the hub’s region get cost-only coverage. You see what they spend, but not the
detections that need the finer telemetry.
Installer, “Choose the hub workspace” panel for a multi-region account, with the region-coverage warning visible naming the workspaces that will get cost-only coverage.
If that matters for your estate, the fix is a second install with a hub in the other
region. Each install keeps its own install_id, and the portal shows both.
If no workspaces are listed
The installer says so rather than leaving you on an empty dropdown. Either the account has no workspaces, or the account you signed in with cannot see them.
Create a workspace in your cloud console, then re-run the installer.
What gets created in the hub
For reference, and so a security reviewer can see it in one place:
- The scheduled job
lakemine-scan - The dashboard “Databricks Cost Optimization”
- The compiled wheel under
/Workspace/Applications/lakemine/artifacts/ - The results schema in the catalog you pick next, default schema name
lakemine - A
lakeminesecret scope holding the subscription key and metering credential - The
lakemine-scanservice principal, created or reused
Your own catalogs, warehouses, and groups are never modified. Everything above is removed by uninstalling.