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 Application Load Balancer
  • Getting started
    • Overview
    • Load balancers
    • HTTP routers
    • Limit on the number of requests
    • Backend groups
    • Target groups
    • Monitoring and logging
    • Monitoring charts
    • Quotas and limits
    • Tips for configuring health checks
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • L7 load balancer logs
  • Release notes
  1. Concepts
  2. Target groups

Target groups

Written by
Yandex Cloud
Updated at June 4, 2026
View in Markdown

An L7 load balancer target group is a set of IP addresses of VMs that your network applications are running on. To enable the load balancer to distribute routing requests between the VMs of the target group, specify it in the backend group configuration.

The main targets in a group are VMs connected to Virtual Private Cloud subnets. For your L7 load balancer to run properly, make sure the target subnets are located in the same cloud network.

You can also add to a target group targets residing outside Virtual Private Cloud, e.g., in your data center connected to Yandex Cloud through Cloud Interconnect. Target IP addresses must belong to the RFC 1918 private address range. For more information, see Subnets.

You can create target groups:

  • Manually. In this case, if you change the VM internal IP address, for example, when moving it to another subnet, make sure to update the target group: first remove the VM and then add the modified VM back to it.
  • Using Instance Groups. When you change the VM configuration, Instance Groups automatically updates IP addresses of VMs in the target group. If the target group is connected to a backend group, Instance Groups also monitors health check results delivered by the L7 load balancer.

You cannot delete a target group used in a backend group. First, you need to remove it from all backend groups.

Use casesUse cases

  • Setting up virtual hosting
  • Creating an L7 load balancer with DDoS protection using the management console or CLI
  • Migrating services from an external NLB to L7 ALB with an internal NLB as a target
  • Migrating services from an NLB with an instance group as a target to an L7 ALB
  • Terminating TLS connections using the management console
  • Writing load balancer logs to PostgreSQL
  • Fault-tolerant website with load balancing via a Yandex Application Load Balancer

Was the article helpful?

Previous
Backend groups
Next
Monitoring and logging
© 2026 Direct Cursus Technology L.L.C.