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
    • 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
    • Overview
    • Network load balancer types
    • Listener
    • Targets and target groups
    • Health checks
    • Implementation specifics
    • Use cases
    • Best practices
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ
  1. Concepts
  2. Network load balancer types

Network load balancer types

Written by
Yandex Cloud
Updated at July 13, 2026
View in Markdown

Note

You can only set the load balancer type (internal or external) when creating it and cannot change it later.

Here are the options for deploying a network load balancer in Yandex Cloud:

  • External load balancer (EXTERNAL), which is created by default. It is used to handle Internet traffic.
  • Internal load balancer (INTERNAL), which is used to handle internal Virtual Private Cloud traffic.

These load balancers operate similarly, but you should keep the following distinctions in mind:

Load balancer property External Internal
Listener IP address Public IP addresses only IP addresses from RFC-1918 only
Blocking the listener target port for traffic on target VMs Active (*) Blocked
Blocking the listener target port for health checks on target VMs Active Active (**)
Locality in traffic processing - Considerations apply
Use of static routes - Considerations apply

Explanation of the table:

  • The VM ports (Target-Port) used to receive traffic from the internal load balancer become unavailable for connection.
    The VMs will only receive traffic from the internal load balancer. The same restriction will not allow a VM from the load balancer's target group to access it through the port being used.
  • (*) A VM from the load balancer's target group cannot access itself through the target port.
  • (**) The health check port (Healthcheck-Port) on target VMs is available for connection if it does not match the target port (Target-Port) of the load balancer listener.

Use casesUse cases

  • Deploying an Always On availability group with an internal network load balancer
  • Connecting to Container Registry from Virtual Private Cloud
  • Connecting to Object Storage from Virtual Private Cloud
  • Implementing fault-tolerant scenarios for NAT VMs
  • Integrating Cloud DNS and a corporate DNS service
  • Migrating services from an NLB to an L7 ALB to enable Yandex Smart Web Security protection

Useful linksUseful links

  • Cloud load balancers: Enhancing availability and fault tolerance

Was the article helpful?

Previous
Overview
Next
Listener
© 2026 Direct Cursus Technology L.L.C.