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
    • Yandex SIEM
    • 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
      • 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:

  • Stopping a load balancer
  • Start a load balancer
  1. Step-by-step guides
  2. L7 load balancers
  3. Stopping and starting an L7 load balancer

Stopping and starting an L7 load balancer

Written by
Yandex Cloud
Updated at July 20, 2026
View in Markdown
  • Stopping a load balancer
  • Start a load balancer

Stopping a load balancerStopping a load balancer

The Stop command stops an L7 load balancer. Once stopped, the load balancer changes its status to STOPPED. As long as the load balancer is stopped, you are not charged for its use.

You can start the load balancer at any time to continue your work. All your data and changes will remain intact.

To stop an L7 load balancer:

Management console
CLI
API
  1. In the management console, select the folder the load balancer is in.

  2. Navigate to Application Load Balancer.

  3. Click next to the load balancer and select Stop.

    To apply this action to multiple load balancers, select the appropriate load balancers in the list, click Stop at the bottom of the screen, and then click Stop in the window that opens.

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.

  1. See the description of the CLI load balancer stop command:

    yc application-load-balancer load-balancer stop --help
    
  2. Get a list of all load balancers in the default folder:

    yc application-load-balancer load-balancer list --format yaml
    

    Result:

    - id: ds79cfnvmti3********
      name: test-load-balancer
      folder_id: b1gv87ssvu49********
      status: ACTIVE
      network_id: enp45glgitd6********
      listeners:
      - name: test-listener
        endpoints:
        - addresses:
          - external_ipv4_address:
              address: 51.250.35.12
          ports:
          - "80"
        http:
          handler:
            http_router_id: ds7bharmjfs3********
      allocation_policy:
        locations:
        - zone_id: ru-central1-a
          subnet_id: e9bn57jvjnbu********
      log_group_id: ckgph76s449v********
      created_at: "2022-02-11T09:00:31.911019416Z"
    - id: ds7o71924t0h********
      name: balancer2
      folder_id: b1gv87ssvu49********
      status: ACTIVE
      network_id: enp45glgitd********
      allocation_policy:
        locations:
        - zone_id: ru-central1-a
          subnet_id: e9bn57jvjnbu********
      log_group_id: ckgjhe81a23v********
      created_at: "2022-02-11T09:01:46.724279145Z"
    
  3. To stop the load balancer, run the following command with its ID or name specified:

    yc application-load-balancer load-balancer stop <load_balancer_name>
    

    For more information about the application-load-balancer load-balancer stop command, see the CLI reference.

Use the stop REST API method for the LoadBalancer resource or the LoadBalancerService/Stop gRPC API call.

Start a load balancerStart a load balancer

The Start command starts an L7 load balancer. Once started, the load balancer changes its status to ACTIVE. From this point on, you start paying for using the load balancer.

To start a load balancer:

Management console
CLI
API
  1. In the management console, select the folder the load balancer is in.

  2. Navigate to Application Load Balancer.

  3. Click next to the load balancer and select Start.

    To apply this action to multiple load balancers, select the appropriate load balancers in the list, click Start at the bottom of the screen, and then click Start in the window that opens.

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.

  1. See the description of the CLI load balancer start command:

    yc application-load-balancer load-balancer start --help
    
  2. Get a list of all load balancers in the default folder:

    yc application-load-balancer load-balancer list --format yaml
    

    Result:

    - id: ds79cfnvmti3********
      name: test-load-balancer
      folder_id: b1gv87ssvu49********
      status: ACTIVE
      network_id: enp45glgitd6********
      listeners:
      - name: test-listener
        endpoints:
        - addresses:
          - external_ipv4_address:
              address: 51.250.35.12
          ports:
          - "80"
        http:
          handler:
            http_router_id: ds7bharmjfs3********
      allocation_policy:
        locations:
        - zone_id: ru-central1-a
          subnet_id: e9bn57jvjnbu********
      log_group_id: ckgph76s449v********
      created_at: "2022-02-11T09:00:31.911019416Z"
    - id: ds7o71924t0h********
      name: balancer2
      folder_id: b1gv87ssvu49********
      status: STOPPED
      network_id: enp45glgitd********
      allocation_policy:
        locations:
        - zone_id: ru-central1-a
          subnet_id: e9bn57jvjnbu********
      log_group_id: ckgjhe81a23v********
      created_at: "2022-02-11T09:01:46.724279145Z"
    
  3. To start a load balancer, run the following command with its ID or name specified:

    yc application-load-balancer load-balancer start <load_balancer_name>
    

    For more information about the application-load-balancer load-balancer start command, see the CLI reference.

Use the start REST API method for the LoadBalancer resource or the LoadBalancerService/Start gRPC API call.

Was the article helpful?

Previous
Getting a log group ID of an L7 load balancer
Next
Moving a VM to a target group in a different availability zone
© 2026 Direct Cursus Technology L.L.C.