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
    • All guides
    • Creating Application Load Balancer infrastructure through a wizard
      • Creating an L7 load balancer
      • Editing an L7 load balancer
      • Getting information about an L7 load balancer
      • Viewing L7 load balancer statistics
      • Setting up alerts
      • Viewing L7 load balancer logs
      • Setting up L7 load balancer logging
      • Getting a log group ID of an L7 load balancer
      • Stopping and starting an L7 load balancer
      • Moving a VM to a target group in a different availability zone
        • Allowing and denying availability zone shutdown
        • Enabling and disabling a zonal shift
      • Deleting an L7 load balancer
    • Viewing service resource operations
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • L7 load balancer logs
  • Release notes

In this article:

  • Allowing availability zone shutdown
  • Denying availability zone shutdown
  1. Step-by-step guides
  2. L7 load balancers
  3. Availability zone management
  4. Allowing and denying availability zone shutdown

Allowing and denying availability zone shutdown

Written by
Yandex Cloud
Updated at July 20, 2026
View in Markdown
  • Allowing availability zone shutdown
  • Denying availability zone shutdown

If an availability zone is under maintenance or shows signs of failure, Yandex Cloud technicians may temporarily shut down that zone. In which case the load balancer will automatically redistribute traffic among the remaining zones. As soon as the zone is back on track, it gets re-enabled, and uniform traffic distribution is resumed.

You can allow or deny auto-disabling an availability zone. However, you cannot select a particular zone to disable. Before allowing the automatic mode, you can try disabling different availability zones.

By default, availability zone shutdown is not allowed.

Allowing availability zone shutdownAllowing availability zone shutdown

CLI
Terraform
API

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

When creating or updating an L7 load balancer, specify the --allow-zonal-shift parameter, e.g.:

yc application-load-balancer load-balancer update \
  <load_balancer_name_or_ID> \
  --allow-zonal-shift

Result:

id: ds70q425egoe********
name: my-balancer
...
allow_zonal_shift: true

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the guides on the Terraform website or its mirror.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

  1. In the configuration file, specify the allow_zonal_shift parameter set to true in the yandex_alb_load_balancer resource description:

    resource "yandex_alb_load_balancer" "my-balancer" {
      ...
      allow_zonal_shift = true
      ...
    }
    
  2. Apply the changes:

    1. In the terminal, navigate to the configuration file directory.

    2. Make sure the configuration is correct using this command:

      terraform validate
      

      If the configuration is valid, you will get this message:

      Success! The configuration is valid.
      
    3. Run this command:

      terraform plan
      

      You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

    4. Apply the configuration changes:

      terraform apply
      
    5. Type yes and press Enter to confirm the changes.

    Terraform will change all required resources. You can check the update in the management console.

    Timeouts

    The Terraform provider limits operations with Application Load Balancer load balancers to 10 minutes.

    Operations in excess of this time will be interrupted.

    How do I modify these limits?

    Add the timeouts section to the load balancer description, e.g.:

    resource "yandex_alb_load_balancer" "<load_balancer_name>" {
      ...
      timeouts {
        create = "60m"
        update = "60m"
        delete = "60m"
      }
    }
    

For more on the properties of the yandex_alb_load_balancer resource, see this provider guide.

To allow zonal shift when creating an L7 load balancer, use the create REST API method for the LoadBalancer resource and set "allowZonalShift": "true", or use the LoadBalancerService/Create gRPC API call and set "allow_zonal_shift": "true".

To allow zonal shift when updating an L7 load balancer, use the update REST API method for the LoadBalancer resource and specify "allowZonalShift": "true", or use the LoadBalancerService/Update gRPC API call with "allow_zonal_shift": "true".

Denying availability zone shutdownDenying availability zone shutdown

CLI
Terraform
API

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

When creating or updating an L7 load balancer, specify the --allow-zonal-shift=false parameter, e.g.:

yc application-load-balancer load-balancer update \
  <load_balancer_name_or_ID> \
  --allow-zonal-shift=false

Result:

id: ds70q425egoe********
name: my-balancer
...

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the guides on the Terraform website or its mirror.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

  1. In the configuration file, specify the allow_zonal_shift parameter set to false in the yandex_alb_load_balancer resource description:

    resource "yandex_alb_load_balancer" "my-balancer" {
      ...
      allow_zonal_shift = false
      ...
    }
    
  2. Apply the changes:

    1. In the terminal, navigate to the configuration file directory.

    2. Make sure the configuration is correct using this command:

      terraform validate
      

      If the configuration is valid, you will get this message:

      Success! The configuration is valid.
      
    3. Run this command:

      terraform plan
      

      You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

    4. Apply the configuration changes:

      terraform apply
      
    5. Type yes and press Enter to confirm the changes.

    Terraform will change all required resources. You can check the update in the management console.

    Timeouts

    The Terraform provider limits operations with Application Load Balancer load balancers to 10 minutes.

    Operations in excess of this time will be interrupted.

    How do I modify these limits?

    Add the timeouts section to the load balancer description, e.g.:

    resource "yandex_alb_load_balancer" "<load_balancer_name>" {
      ...
      timeouts {
        create = "60m"
        update = "60m"
        delete = "60m"
      }
    }
    

For more on the properties of the yandex_alb_load_balancer resource, see this provider guide.

To deny zonal shift when creating an L7 load balancer, use the create REST API method for the LoadBalancer resource and set "allowZonalShift": "false", or use the LoadBalancerService/Create gRPC API call and set "allow_zonal_shift": "false".

To deny zonal shift when updating an L7 load balancer, use the update REST API method for the LoadBalancer resource and specify "allowZonalShift": "false", or use the LoadBalancerService/Update gRPC API call with "allow_zonal_shift": "false".

What's next {whats-next}What's next

Enabling and disabling a zonal shift

Was the article helpful?

Previous
Moving a VM to a target group in a different availability zone
Next
Enabling and disabling a zonal shift
© 2026 Direct Cursus Technology L.L.C.