Yandex Cloud
Поиск
Связаться с намиПодключиться
  • Истории успеха
  • Документация
  • Блог
  • Все сервисы
  • Статус работы сервисов
    • Доступны в регионе
    • Инфраструктура и сеть
    • Платформа данных
    • Контейнеры
    • Инструменты разработчика
    • Бессерверные вычисления
    • Безопасность
    • Мониторинг и управление ресурсами
    • ИИ для бизнеса
    • Бизнес-инструменты
  • Все решения
    • По отраслям
    • По типу задач
    • Экономика платформы
    • Безопасность
    • Техническая поддержка
    • Каталог партнёров
    • Обучение и сертификация
    • Облако для стартапов
    • Облако для крупного бизнеса
    • Центр технологий для общества
    • Партнёрская программа
    • Поддержка IT-бизнеса
    • Облако для фрилансеров
    • Обучение и сертификация
    • Блог
    • Документация
    • Мероприятия и вебинары
    • Контакты, чаты и сообщества
    • Идеи
    • Тарифы Yandex Cloud
    • Промоакции и free tier
    • Правила тарификации
  • Истории успеха
  • Документация
  • Блог
Проект Яндекса
© 2025 ТОО «Облачные Сервисы Казахстан»
Terraform в Yandex Cloud
  • Начало работы
  • Библиотека решений
    • Обзор
    • История изменений (англ.)
          • lb_network_load_balancer
          • lb_target_group

В этой статье:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for target
  • Nested Schema for timeouts
  • Import
  1. Справочник Terraform
  2. Ресурсы (англ.)
  3. Network Load Balancer (NLB)
  4. Resources
  5. lb_target_group

yandex_lb_target_group (Resource)

Статья создана
Yandex Cloud
Обновлена 20 октября 2025 г.
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for target
    • Nested Schema for timeouts
  • Import

A TargetGroup resource. For more information, see Target groups and resources.

Example usageExample usage

//
// Create a new NLB Target Group.
//
resource "yandex_lb_target_group" "my_tg" {
  name      = "my-target-group"
  region_id = "ru-central1"

  target {
    subnet_id = yandex_vpc_subnet.my-subnet.id
    address   = yandex_compute_instance.my-instance-1.network_interface.0.ip_address
  }

  target {
    subnet_id = yandex_vpc_subnet.my-subnet.id
    address   = yandex_compute_instance.my-instance-2.network_interface.0.ip_address
  }
}

SchemaSchema

OptionalOptional

  • description (String) Description of the target group. 0-256 characters long.
  • folder_id (String) ID of the folder that the target group belongs to.
  • id (String) ID of the TargetGroup resource to return.
    To get the target group ID, use a [TargetGroupService.List] request.
  • labels (Map of String) Resource labels as key:value pairs. Maximum of 64 per resource.
  • name (String) Name of the target group.
    The name is unique within the folder. 3-63 characters long.
  • region_id (String) ID of the region where the target group resides.
  • target (Block Set) A list of targets in the target group. (see below for nested schema)
  • target_group_id (String) ID of the TargetGroup resource to return.
    To get the target group ID, use a [TargetGroupService.List] request.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • created_at (String) Output only. Creation timestamp in RFC3339 text format.

Nested Schema for Nested Schema for target

Optional:

  • address (String) IP address of the target.
  • subnet_id (String) ID of the subnet that targets are connected to.
    All targets in the target group must be connected to the same subnet within a single availability zone.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • read (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
  • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

ImportImport

The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console or YC CLI.

# terraform import yandex_lb_target_group.<resource Name> <resource Id>
terraform import yandex_lb_target_group.my_tg ...

Была ли статья полезна?

Предыдущая
lb_network_load_balancer
Следующая
storage_bucket
Проект Яндекса
© 2025 ТОО «Облачные Сервисы Казахстан»