Yandex.Cloud
  • Services
  • Why Yandex.Cloud
  • Pricing
  • Documentation
  • Contact us
Get started
Yandex Network Load Balancer
  • Getting started
  • Step-by-step instructions
    • All instructions
    • Network load balancers
      • Create a network load balancer
      • Create an internal network load balancer
      • Start a load balancer
      • Stop a load balancer
      • Delete a load balancer
      • Check target health statuses
      • Add a listener
      • Delete a listener
    • Target groups
      • Create a target group
      • Attach a target group to a load balancer
      • Detach a target group from a load balancer
      • Delete a target group
  • Concepts
    • Network load balancer
    • Internal network load balancer
    • Listener
    • Targets and groups
    • Resource health checks
    • Quotas and limits
  • Best practices for using the service
  • Access management
  • Pricing policy
  • API reference
    • Authentication in the API
    • gRPC
      • Overview
      • NetworkLoadBalancerService
      • TargetGroupService
      • OperationService
    • REST
      • Overview
      • NetworkLoadBalancer
        • Overview
        • addListener
        • attachTargetGroup
        • create
        • delete
        • detachTargetGroup
        • get
        • getTargetStates
        • list
        • listOperations
        • removeListener
        • start
        • stop
        • update
      • TargetGroup
        • Overview
        • addTargets
        • create
        • delete
        • get
        • list
        • listOperations
        • removeTargets
        • update
      • Operation
        • Overview
        • get
  • Questions and answers
  1. Concepts
  2. Internal network load balancer

Internal network load balancer

  • Guidelines and limitations

The feature is at the Preview stage.

An internal network load balancer is used to balance traffic between resources that are connected:

  • To VPC subnets.
  • Via VPN.
  • Via Cloud Interconnect.

An internal network load balancer has the same purpose and traffic balancing mechanism as an external load balancer: the traffic is distributed across the resources of the target groups connected to the load balancer.

The listener of an internal load balancer uses an internal IP address from the subnet it runs in. You can connect the load balancer to any subnet from any availability zone: actually, it will be present in all the subnets that includes target resources connected to the balancer.

Guidelines and limitations

When you use an internal network load balancer, keep in mind the following:

  1. An internal IP address is assigned to the balancer randomly from the subnet's address range.
  2. The VM ports used to receive the traffic from the load balancer and to check status become unavailable when a VM is connected to an internal balancer. The VM will only receive traffic from the load balancer.
Language
Careers
Privacy policy
Terms of use
© 2021 Yandex.Cloud LLC