Skip to content

Cloud & infrastructure

Connect a Nebius AI Cloud tenant with a read-only service account, plus optional just-in-time write elevation.

Nebius connects one tenant, with all its projects, through a reader service account Dave uses on its own, plus an optional writer service account Dave uses only for writes you approve. Dave reads with the official nebius CLI and looks up Nebius documentation through the Nebius docs MCP server.

You never paste a key. Dave generates a key pair for each service account and keeps the private key encrypted on its side; the setup script only uploads the public key. The sandbox gets a short-lived access token, never the private key.

  1. In the Nebius console, copy the tenant ID from Administration → Tenant settings — it starts with tenant-.

  2. In Dave, go to Integrations → Add integration → Nebius.

  3. Paste the Tenant ID and set a Label — see labels.

  4. Optionally paste the Billing contract ID — see Billing.

  5. Optionally tick Enable agentic JIT — see Just-in-time elevation.

  6. Choose Connect Nebius Tenant. Dave shows a one-line setup command.

  7. Open Cloud Shell in the Nebius console as a tenant admin (a member of admins) and run the command. Re-running it is safe.

  8. Return to Dave. It signs in as the reader and lists the tenant’s projects to finish.

The setup script creates these service accounts in the tenant’s first project and adds them to the tenant’s default groups:

Service account Group Role on the tenant Used for
dave-reader-<id> viewers viewer Every read
dave-writer-<id> admins admin Only writes you approve (JIT)

The writer is created only when JIT is enabled. <id> is the start of the Dave integration ID, so you can connect several tenants — or the same tenant twice — under different labels without the connections sharing service accounts.

The viewer role includes the tenant’s billing and usage data.

To let Dave report the tenant’s costs, add its billing contract ID:

  1. In the Nebius console, go to Billing → Payments, open the Billing details tab, and copy the contract ID from the Payer section. It starts with contract-.

  2. In Dave, open the Nebius integration and paste it into Billing contract ID under Billing. You can also set it when you connect.

With JIT enabled, a write runs as an approved runbook action. For that one command, Dave signs in as the writer, passes the token to the nebius CLI as NEBIUS_IAM_TOKEN, and revokes the writer’s tokens as soon as the command ends.

If you connected before Dave’s writer was an admin, click Reconnect and run the new setup command to upgrade it.

Disconnecting shows a teardown command. Run it in Cloud Shell to delete both service accounts and groups; Dave confirms the reader can no longer sign in.

  • Setup stays on “Run the setup script” — the script did not reach Dave. Re-run it and check its last line says Done.
  • “Nebius rejected the service account” — the public key or access permit was removed. Re-run the setup script, then reconnect.
  • Billing exports fail with an invalid contract — copy the ID again from Billing details.
  • PermissionDenied while running the script — run it as a tenant admin, and set up billing first — Nebius refuses key uploads in tenants without billing.