Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • 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
© 2025 Direct Cursus Technology L.L.C.
Yandex Application Load Balancer
  • Getting started
    • All guides
    • Creating Application Load Balancer infrastructure through a wizard
      • Creating a backend group
      • Getting information about a backend group
      • Editing a backend group
      • Deleting a backend group
    • Viewing service resource operations
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • L7 load balancer logs
  • Release notes
  1. Step-by-step guides
  2. Backend groups
  3. Getting information about a backend group

Getting information about a backend group

Written by
Yandex Cloud
Updated at July 29, 2025
Management console
CLI
Terraform
API
  1. In the management console, select the folder with your backend group.
  2. From the list of services, select Application Load Balancer.
  3. In the left-hand panel, select Backend groups.
  4. Select your backend group.
  5. You will see your group details on the Overview page.

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

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

  1. See the description of the CLI command for getting backend group information:

    yc alb backend-group get --help
    
  2. To get information about a backend group, run this command with its name or ID specified:

    yc alb backend-group get <backend_group_name>
    

    Result:

    id: ds7maho6c4or********
    name: alb-bg
    folder_id: b1geoelk7fld********
    http:
      backends:
        - name: backend-1
          backend_weight: "1"
          port: "80"
          target_groups:
            target_group_ids:
              - ds7cjrs15ero********
          healthchecks:
            - timeout: 10s
              interval: 2s
              healthcheck_port: "80"
              http:
                path: /
    created_at: "2023-10-24T12:22:20.870326850Z"
    

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 relevant documentation on the Terraform website or its mirror.

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

To get backend group information using Terraform:

  1. Add the data and output sections to the Terraform configuration file:

    data "yandex_alb_backend_group" "my_bg" {
      backend_group_id = "<backend_group_ID>"
    }
    
    output "backend_group" {
      value = data.yandex_alb_backend_group.my_bg.http_backend
    }
    

    Where:

    • data "yandex_alb_backend_group": Description of the backend group as a data source:
      • backend_group_id: Backend group ID.
    • output "backend_group": Output variable with information about the connected HTTP backend:
      • value: Return value.

    You can replace http_backend with another variable to get the information you need. For more information about the yandex_alb_backend_group data source variables, see the provider documentation.

  2. Create the resources:

    1. In the terminal, go to the directory where you edited the configuration file.

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

      terraform validate
      

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

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

      terraform plan
      

      You will see a detailed list of resources. No changes will be made at this step. If the configuration contains any errors, Terraform will show them.

    4. Apply the changes:

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

    Terraform will create the required resources and display their output variables. To check the results, run this command:

    terraform output
    

    Result:

    backend_group = tolist([
      {
        "healthcheck" = tolist([
          {
            "grpc_healthcheck" = tolist([])
            "healthcheck_port" = 80
            "healthy_threshold" = 1
            "http_healthcheck" = tolist([
              {
                "host" = ""
                "http2" = false
                "path" = "/health"
              },
            ])
            "interval" = "1s"
            "interval_jitter_percent" = 0
            "stream_healthcheck" = tolist([])
            "timeout" = "1s"
            "unhealthy_threshold" = 1
          },
          ...
    

To get backend group details, use the get REST API method for the BackendGroup resource or the BackendGroupService/Get gRPC API call.

Was the article helpful?

Previous
Creating a backend group
Next
Editing a backend group
© 2025 Direct Cursus Technology L.L.C.