Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nebius.com/llms.txt

Use this file to discover all available pages before exploring further.

Nebius AI Cloud resources within one network can connect directly to each other by using their private IP addresses. If you want to disable connectivity between resources or allocate the same private IP address to multiple different resources, for example, for testing purposes, create separate networks for them.

​
Prerequisites

  1. Make sure you are in a group that has at least the editor role within your tenant; for example, the default editors group. You can check this in the Administration → IAM section of the web console.
  2. Install and initialize the Nebius AI Cloud CLI.
  3. Install jq to extract IDs and tokens from the JSON data returned by the Nebius AI Cloud CLI: 
    sudo apt-get install jq

​
Create a network and a subnet

Each network must contain at least one subnet. To create a network and a subnet within it, run the following command: 
export NETWORK_ID=$(nebius vpc network create \
   --name <network_name> \
   --format json | jq -r ".metadata.id")
export SUBNET_ID=$(nebius vpc subnet create \
   --name <subnet_name> \
   --network-id $NETWORK_ID \
   --format json | jq -r ".metadata.id")
This command saves the IDs of the created network and subnet to environment variables that you can use to create resources.

​
Add resources to a network or subnet

Set the required network or subnet when you create Nebius AI Cloud resources. You cannot move a resource to another network or subnet after creation.
When you create resources by using the Nebius AI Cloud CLI, set the network or subnet by using parameters with network-id or subnet-id in them. For example:
Postgres, PostgreSQL and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada, and used with their permission.