By default, Nebius AI Cloud routes egress traffic from your resources according to the default routing rules. You can configure routing by creating and managing routing tables (route tables) and routes. For more details on how routing works, see Routing in Nebius AI Cloud.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.
Prerequisites
- Web console
- CLI
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.Creating routing tables
- Web console
- CLI
-
In the sidebar, go to
Network.
- Select the network for which you want to create a routing table. You can only assign a routing table to subnets within this network.
- Click Create and select Routing table.
-
In the window that opens:
- Enter a name for the routing table.
- (Optional) Select the subnets within this network that you want to assign to the routing table. You can also assign a routing table to subnets later.
- Click Create. The new routing table should appear on the Routing tables tab.
Adding routes to routing tables
Routes support different next hop options. You can set the next hop to an allocation or to the internet through the default egress gateway. For more information, see Routing in Nebius AI Cloud.- Web console
- CLI
-
In the sidebar, go to
Network.
- Select the network that contains the routing table and switch to the Routing tables tab.
- Select the routing table to which you want to add a route.
- Click Add route.
-
In the window that opens:
- Enter a name for the route.
-
In Destination CIDR, do one of the following:
- To route traffic to an allocation, specify the CIDR block of destination IP addresses to which the route applies.
- To route traffic to the internet through the default egress gateway, specify
0.0.0.0/0.
-
Under Next hop, do one of the following:
- To route traffic to an allocation, select Allocation.
- To route traffic to the internet, select Default egress gateway.
- Only if you selected Allocation under Next hop, select the allocation to route traffic through.
- Click Add route.
Deleting routes
- Web console
- CLI
-
In the sidebar, go to
Network.
- Select the network that contains the routing table and switch to the Routing tables tab.
- Select the routing table from which you want to delete a route.
-
Do one of the following:
- To delete one route, click
next to the route and select Delete.
- To delete multiple routes at once, select the checkboxes next to the required routes and click Delete in the banner that appears.
- To delete one route, click
Assigning routing tables to subnets
You can only assign a routing table to subnets within the network that the routing table is associated with. After you assign a routing table to a subnet, egress traffic from all resources in the subnet is routed according to the routing table.- Web console
- CLI
- In the sidebar, go to
Network.
- Switch to the Subnets tab.
- Select the subnet to which you want to assign a routing table.
- On the Settings tab, select a routing table from the Routing table drop-down list.
- Click Save changes.
Reverting subnets to the parent network’s default routing table
If you no longer want to apply custom routing to a subnet, you can unassign its custom routing table. After this, the subnet uses its parent network’s default routing table.- Web console
- CLI
To assign the subnet to its parent network’s default routing table:
- Find the parent network’s default routing table:
- In the sidebar, go to
Network.
- In the list of networks, select the network to which the subnet belongs.
- Switch to the Routing tables tab. The default routing table has a Default label next to its name.
- In the sidebar, go to
- Assign the default routing table to the subnet:
- Switch to the Subnets tab.
- Select the subnet that you want to revert to the default routing table.
- On the Settings tab, select the default routing table from the Routing table drop-down list.
- Click Save changes.
Resetting default routing tables of networks
Reverting to the default routing table means that the default routing rules apply to the subnet again, unless you have modified the default routing table. If you modified it, you can make the default routing table implement the default routing rules again. To do this, bring it to the state described in Default routing tables:- Web console
- CLI
If you added new routes to the default routing table, you can delete them to reset the default routing table.
-
In the sidebar, go to
Network.
- Select the network whose default routing table you want to reset.
- Switch to the Routing tables tab.
- Select the routing table that is labeled Default.
-
In the routes list, check whether there is a route whose Destination CIDR value is
0.0.0.0/0. -
If there is no such route:
- Click Add route.
-
In the window that opens:
- Specify a name for the route.
- In Destination CIDR, enter
0.0.0.0/0. - Under Next hop, select Default egress gateway.
- Click Add route.
- Delete all other routes from the default routing table.
Deleting routing tables
- Web console
- CLI
- In the sidebar, go to
Network.
- Select the network from which you want to delete the routing table and switch to the Routing tables tab.
- Click
next to the routing table you want to delete.
- In the window that opens:
- If the routing table is not assigned to any subnets, confirm the deletion.
- If the routing table is assigned to a subnet, select a new routing table for the subnet or choose the option to use the default routing table, then confirm the deletion.