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
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Network Load Balancer
  • Getting started
    • Overview
    • Network load balancer types
    • Traffic listener
    • Target groups and resources
    • Health checks
    • Implementation specifics
    • Use cases
    • Recommendations for use
    • 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 May 5, 2025

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:

  • An external load balancer (EXTERNAL) is created by default. It is used to handle Internet traffic.
  • An internal load balancer (INTERNAL) is used for handling traffic within Virtual Private Cloud.

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 blocked
Locality in traffic processing - specifics apply
Use of static routes - specifics apply

Explanation of the table:

  • The VM ports (Target-Port) used to receive traffic from the internal load balancer and health checks become unavailable for connecting.
    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.

Was the article helpful?

Previous
Overview
Next
Traffic listener
© 2025 Direct Cursus Technology L.L.C.