Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
All solutions
    • All solutions for Compute Cloud
    • You are unable to add a Committed Volume of Services (CVoS) for Compute Cloud
    • You see a "Permission denied" error when connecting to a VM created in Terraform
    • No nested virtualization support
    • UEFI support and data import from GPT-formatted disks
    • Fixing the "Not enough resources" error on launching a virtual machine
    • Recovering access to a VM with a lost SSH key
    • Fixing issues with creating disk snapshots
    • Boot disk size failed to increase
    • VM instance shuts down on the "instance guest stop processing" operation
    • Fixing the "WARNING REMOTE HOST IDENTIFICATION HAS CHANGED" error
    • Fixing a non-replicable disk breakdown
    • Fixing connection issues with Kosmos VM
    • Fixing password reset issues for VMs based on a Kosmos image
    • Options to migrate a VM image to Yandex Cloud
    • Changing the boot disk for an instance to SSD
    • Getting details about RAM consumption for Compute Cloud instances
    • Creating VMs having multiple network interfaces
    • Decreasing VM disk size
    • Exporting disk images of Compute Cloud VM instances
    • Transferring VMs between folders or clouds
    • Setting up GUI and graphic environment on Linux VMs
    • Using an ISO image for deploying VM instances
    • Monitoring incoming or outgoing VM traffic
    • How to use WinSCP to connect to a Linux VM in Yandex Cloud with a key generated at VM creation
    • How to back up a VM with rollback support
    • How to connect via SSH as root with a password or key
    • How to track memory usage
    • How to save snapshots and images locally
    • How to change an internal IP address
    • How to read the "Connections quota utilization" chart
    • What is the disk access speed for a VM
    • How to create a VM with password access
    • What is the maximum number of network interfaces that can be connected to a VM

In this article:

  • Issue description
  • Solution
  1. Compute Cloud
  2. Creating VMs having multiple network interfaces

Creating VMs having multiple network interfaces

Written by
Yandex Cloud
Updated at October 2, 2024
  • Issue description
  • Solution

Issue descriptionIssue description

You need to create a VM with more than one network interface.

SolutionSolution

To create a VM with multiple network interfaces, use images from the Network infrastructure category in Yandex Cloud Marketplace. Images from this category allow you to create instances with multiple interfaces used to connect to different cloud networks.

As an option, you can use the NAT instance image based on an LTS release of Ubuntu Linux. In the documentation section, you can find a scenario for setting up egress traffic routing on a VM instance based on this image.

If you are familiar with to Cisco or Mikrotik solutions, you can use them as virtual routers: images for such products are also available in Yandex Cloud Marketplace, but you need to purchase a license to use them.
You can find more details about these products here:

  • Installing a Cisco CSR 1000v virtual router.
  • Installing a Mikrotik CHR virtual router.

Maximum number of network interfaces depends on the platform and vCPU on your VM.
Here are the current limits on the number of network interfaces for hardware platforms used in Yandex Cloud:

Broadwell (standard-v1):

  • 2 to 16 vCPUs: 8 interfaces
  • 20 to 32 vCPUs: 16 interfaces

Cascade Lake (standard-v2):

  • 2 to 16 vCPUs: 8 interfaces
  • 20 to 80 vCPUs: 16 interfaces

For Ice Lake (standard-v3):

  • 2 to 32 vCPUs: 8 interfaces
  • 36 to 96 vCPUs: 16 interfaces

Note that when a VM is starting, a maximum of 14 devices, including the boot disk and a NIC, can be connected to it. A VM will not start if it has more than 14 connected devices. Keep this in mind when creating the VM. More devices should be connected to a running VM, if needed.
For more information, see the documentation article.

Alert

If you restart a VM with more than 14 connected devices, it will not start up.

Was the article helpful?

Previous
Getting details about RAM consumption for Compute Cloud instances
Next
Decreasing VM disk size
Yandex project
© 2025 Yandex.Cloud LLC