Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Network Load Balancer
  • Getting started
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Getting started
  • Create a target group
  • Create a network load balancer
  • Check the resource status
  • Delete the load balancer and the resources you created
  • What's next

Getting started with Network Load Balancer

Written by
Yandex Cloud
Improved by
Danila N.
Updated at September 7, 2026
View in Markdown
  • Getting started
  • Create a target group
  • Create a network load balancer
  • Check the resource status
  • Delete the load balancer and the resources you created
  • What's next

Network load balancers evenly distribute traffic evenly across cloud resources and monitor their health status. This enhances the availability and fault tolerance of your apps and cloud network infrastructure.

Create a network load balancer with a listener, attach a target group, and set up health checks using Network Load Balancer.

Getting startedGetting started

  1. Log in to the management console or sign up. If not signed up yet, navigate to the management console and follow the on-screen instructions.
  2. On the Yandex Cloud Billing page, make sure you have a linked billing account with the ACTIVE or TRIAL_ACTIVE status. If you do not have a billing account yet, create one.
  3. If you do not have a folder yet, create one.
  4. Create multiple VMs in advance to include them in the target group attached to your network load balancer. For testing, consider using low-cost preemptible VMs.

Create a target groupCreate a target group

A target group consists of cloud resources that receive traffic from the network load balancer.

To create a target group:

  1. In the management console, select the folder where you want to create a target group.
  2. Navigate to Network Load Balancer.
  3. In the left-hand panel, select Target groups.
  4. Click Create a target group.
  5. Enter test-target-group as the target group name.
  6. Select the VMs to add to the target group.
  7. Click Create.

Create a network load balancerCreate a network load balancer

When creating a network load balancer, you need to set up a listener to handle incoming traffic and configure health checks for the targets in the attached target group.

To create a network load balancer:

  1. In the management console, select the folder where you need to create a load balancer.
  2. Navigate to Network Load Balancer.
  3. Click Create a network load balancer.
  4. Name the load balancer, e.g., test-load-balancer.
  5. Select the load balancer's Type: External.
  6. In the Public address field, select an IP address assignment method:

    • Auto: Assign a random IP address from the Yandex Cloud IP address pool. In this case, you can enable DDoS protection using the option below.
    • List: To select a public IP address from the list of previously reserved static addresses. For more information, see Converting a dynamic public IP address to static.
  7. Under Listeners, add a listener:

    1. Click Add listener.
    2. In the window that opens, specify these listener settings:

      • Name.

      • Protocol: TCP or UDP.

        Note

        By default, the listener uses TCP. To use UDP, contact technical support.

      • Port where the listener will listen for incoming traffic. The possible values range from 1 to 32767.

      • Target port to which the load balancer will redirect traffic. The possible values range from 1 to 32767.

    3. Click Add.
  8. Under Target groups, select the previously created target group.
  9. Optionally, under Health check, click Configure. In the window that opens, specify the resource health check settings:

    1. Name. The naming requirements are as follows:

      • Length: between 3 and 63 characters.
      • It can only contain lowercase Latin letters, numbers, and hyphens.
      • It must start with a letter and cannot end with a hyphen.
    2. Type: HTTP, TCP, HTTP/2, HTTPS, or GRPC.

    3. Path: Specify a URL for health checks (for the HTTP, HTTP/2, HTTPS, and GRPC types).

    4. Host: Specify a host (for the HTTP/2, HTTPS, and GRPC types).

    5. Port for health checks. The possible values range from 1 to 32767.

    6. Timeout in sec: Response timeout in seconds. The possible values range from 1 to 60. The interval must be at least 1 second longer than the response timeout.

    7. Interval in sec: Health check interval in seconds. The possible values range from 1 to 60.

    8. Healthy threshold: Number of successful checks required to consider a VM instance ready to receive traffic.

    9. Unhealthy threshold: Number of failed checks before traffic is no longer routed to the VM.

    10. Click Apply.

  10. Click Create.

Check the resource statusCheck the resource status

To check the status of the network load balancer and targets in the attached target group:

  1. In the management console, select the folder where you need to create a load balancer.
  2. Navigate to Network Load Balancer.
  3. In the list, find the load balancer you created.
  4. Make sure the load balancer's status is Active, which means it is ready to distribute traffic across the targets.
  5. Click the load balancer name.
  6. Check Target groups. If the VMs are running and ready to receive traffic, their status must be HEALTHY.
  7. Open the Compute Cloud page and stop one of the VMs in the target group.
  8. Go back to the load balancer page and make sure the stopped VM's status is now UNHEALTHY. This means the target in the group failed the health check and is not ready to receive traffic.

Delete the load balancer and the resources you createdDelete the load balancer and the resources you created

If you no longer need the load balancer, delete it.

Then, delete the target group and VMs.

What's nextWhat's next

  • Learn more about how network load balancers work here.
  • See our best practices for deploying a network load balancer.

Was the article helpful?

Next
All guides
© 2026 Direct Cursus Technology L.L.C.