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 Application Load Balancer
  • Getting started
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • L7 load balancer logs
  • Release notes

In this article:

  • Q4 2024
  • Q2 2024
  • Q1 2024

Yandex Application Load Balancer release notes

Written by
Yandex Cloud
Updated at February 17, 2025
  • Q4 2024
  • Q2 2024
  • Q1 2024

Q4 2024Q4 2024

  • Added the Global RateLimit module you can use to set a limit on the number of HTTP and gRPC requests to a virtual host. You can set this limit for the entire virtual host or its individual route.

    This feature is at the Preview stage. To access this feature, contact support.

  • You can now add your own HTTP status codes that backend health checks will treat as correct. Code values can range from 100 to 599.

  • Added an option of keeping a connection alive even if the health check fails. This option is only available for Stream checks.

  • Added an option to set an idle timeout for Stream and SNI listeners.

  • Added a description of the x_forwarded_for field that is provided in load balancer logs.

All new features are currently supported in the CLI, API, and Terraform interfaces.

Q2 2024Q2 2024

  • Added validation of internal IPv4 addresses when creating or updating a load balancer.
  • Fixed the validation issue when creating and updating a target group that could place a backend without a specified weight in a group of backends with specified weights.

Q1 2024Q1 2024

  • Improved stability of data processing and transmission (data plane) within the service.
  • Implemented integration with Yandex Smart Web Security:
    • Connecting a virtual host to a security profile (management console, CLI, Terraform, API).
    • Sending Smart Web Security event logs to a Yandex Cloud Logging log group.
    • Sending Smart Web Security metrics to Yandex Monitoring.
  • Changed behavior of the load balancer with Stream backend groups: now connections to a backend will be closed if the backend fails a health check.
  • Optimized the process of working with the list of operations with service resources.
  • Added the ability to search for a load balancer in the management console by internal IP address.
  • Added the ability to granularly place load balancer nodes in different availability zones using the management console.
  • Improved the Terraform provider performance: eliminated the validation error when changing a load balancer listener's type from TLS to Stream and vice versa.

Was the article helpful?

Previous
L7 load balancer logs
© 2025 Direct Cursus Technology L.L.C.