Nebius#
Service account#
A service account lets SkyPilot use Nebius without a personal access token, which expires. Use one for a shared API server, CI, or any long-running setup.
You need the Nebius CLI, signed in as a user who can manage service accounts and groups in your tenant.
Important
The service account needs the editor role in your tenant (step 2 grants
it). Without it, sky check nebius and launches fail with a permission
error.
Set the IDs used below. Fill these in once; you can then paste every later command unchanged.
# Tenant ID: from the web console, or `nebius iam tenant list`. export NEBIUS_TENANT_ID=<tenant id> # Project to hold the service account: from the web console, or # `nebius iam project list --parent-id $NEBIUS_TENANT_ID`. export NEBIUS_PROJECT_ID=<project id> # Name of the service account to create, or of an existing one. export NEBIUS_SA_NAME=skypilot
Create the service account and give it the editor role. If the account already exists,
service-account createreports that and the rest still runs.nebius iam service-account create \ --parent-id $NEBIUS_PROJECT_ID \ --name $NEBIUS_SA_NAME export NEBIUS_SA_ID=$(nebius iam service-account get-by-name \ --parent-id $NEBIUS_PROJECT_ID \ --name $NEBIUS_SA_NAME \ --format jsonpath='{.metadata.id}') # Editor role: add the account to the tenant's editors group. export NEBIUS_EDITORS_GROUP_ID=$(nebius iam group get-by-name \ --parent-id $NEBIUS_TENANT_ID \ --name editors \ --format jsonpath='{.metadata.id}') nebius iam group-membership create \ --parent-id $NEBIUS_EDITORS_GROUP_ID \ --member-id $NEBIUS_SA_ID
Save its key and your tenant ID where SkyPilot reads them (more on authorized keys):
nebius iam auth-public-key generate \ --service-account-id $NEBIUS_SA_ID \ --output ~/.nebius/credentials.json echo $NEBIUS_TENANT_ID > ~/.nebius/NEBIUS_TENANT_ID.txt
Verify. SkyPilot prefers an access token in
~/.nebius/NEBIUS_IAM_TOKEN.txt(the installation guide creates one) over the service account, so remove it first:rm -f ~/.nebius/NEBIUS_IAM_TOKEN.txt sky check nebius
Nebiusshould be listed under Enabled infra.
Next steps:
To use this service account with a remote API server, see Optional: Configure cloud accounts (Nebius tab).
To use a different service account per workspace, set
nebius.credentials_file_pathin the workspace config.Nebius Object Storage uses a separate access key; see the Nebius section of the installation guide.
Using internal IPs#
For security reasons, users may only want to use internal IPs for SkyPilot instances.
To do so, you can update the SkyPilot config (for a remote API server, through the dashboard) to specify the nebius.use_internal_ips and nebius.ssh_proxy_command fields (to see the detailed syntax, see Advanced Configuration):
nebius:
use_internal_ips: true
ssh_proxy_command: ssh -W %h:%p -o StrictHostKeyChecking=no myself@my.proxy
The nebius.ssh_proxy_command field is optional. If SkyPilot is run on a machine that can directly access the internal IPs of the instances, it can be omitted. Otherwise, it should be set to a command that can be used to proxy SSH connections to the internal IPs of the instances.
Using static IPs#
To ensure your VM’s IP address remains static across stop-start operations, set the nebius.use_static_ip_address field in SkyPilot’s global config file (~/.sky/config.yaml). For a detailed syntax reference, see Advanced Configuration.
nebius:
use_static_ip_address: true
Note
This makes the VM’s public IP static, so it has no effect when
nebius.use_internal_ips is true.
Spot VMs#
Set resources.use_spot: true to explicitly accept the current Nebius spot
price. SkyPilot launches price-taking VMs; no pricing policy is required.
Prices can change while a VM runs, and SkyPilot does not set a maximum bid.
Displayed costs are estimates; max_hourly_cost filters estimated costs
and does not enforce a running price limit.
Use sky jobs launch task.yaml for managed recovery after preemption.
Migrating existing preemptible VMs#
Upgrading SkyPilot does not opt existing VMs into spot pricing. When Nebius enables auctions for a region and SKU, legacy preemptible VMs are stopped and cannot restart until their owners explicitly opt in.
To preserve an existing cluster:
Stop it with
sky stop <cluster-name>if it is still running.Using the Nebius console or API, explicitly select price-taking spot pricing for each stopped VM, including the head and workers. In the API, set
spec.follows_spot_priceto{}and preserve the other VM settings.Run
sky start <cluster-name>after every VM has been opted in.
SkyPilot reports a migration error when asked to restart a legacy VM; it does not change the VM’s pricing consent automatically.