Creating an Application Load Balancer target group

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 creating a target group:

   yc alb target-group create --help
   

2. Run this command, with the target group name, subnet name, and VM’s internal IP addresses specified:

   yc alb target-group create \
     --name <target_group_name> \
     --target subnet-name=<subnet_name>,ip-address=<VM_1_internal_IP_address> \
     --target subnet-name=<subnet_name>,ip-address=<VM_2_internal_IP_address> \
     --target subnet-name=<subnet_name>,ip-address=<VM_3_internal_IP_address>
   

   Result:

   id: a5d751meibht********
   name: <target_group_name>
   folder_id: aoerb349v3h4********
   targets:
   - ip_address: <VM_1_internal_IP_address>
     subnet_id: fo2tgfikh3he********
   - ip_address: <VM_2_internal_IP_address>
     subnet_id: fo2tgfikh3he********
   - ip_address: <VM_3_internal_IP_address>
     subnet_id: fo2tgfikh3he********
   created_at: "2021-02-11T11:16:27.770674538Z
   

   You can also create a target group with resources outside Yandex Virtual Private Cloud, e.g., in your data center connected to Yandex Cloud via Yandex Cloud Interconnect. Target IP addresses must belong to the RFC 1918 private address range. For more information, see Subnets.

   Run this command, with the target group name and resource’s private IPv4 addresses specified:

   yc alb target-group create \
     --name <target_group_name> \
     --target private-ip-address=true,ip-address=<resource_1_IPv4_private_address> \
     --target private-ip-address=true,ip-address=<resource_2_IPv4_private_address> \
     --target private-ip-address=true,ip-address=<resource_3_IPv4_private_address>
   

   Result:

   id: ds7s2dld2usr********
   name: <target_group_name>
   folder_id: aoerb349v3h4********
   targets:
     - ip_address: <resource_1_IPv4_private_address>
       private_ipv4_address: true
     - ip_address: <resource_2_IPv4_private_address>
       private_ipv4_address: true
     - ip_address: <resource_3_IPv4_private_address>
       private_ipv4_address: true
   created_at: "2023-07-25T08:55:14.172526884Z"
   

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.

1. In the Terraform configuration file, specify your new resource settings:

   resource "yandex_alb_target_group" "foo" {
     name           = "<target_group_name>"
   
     target {
       subnet_id    = "<subnet_ID>"
       ip_address   = "<VM_1_internal_IP_address>"
     }
   
     target {
       subnet_id    = "<subnet_ID>"
       ip_address   = "<VM_2_internal_IP_address>"
     }
   
     target {
       subnet_id    = "<subnet_ID>"
       ip_address   = "<VM_3_internal_IP_address>"
     }
   }
   

   Where yandex_alb_target_group specifies target group settings:

   • name: Target group name.
   • target: Target settings:
     • subnet_id: ID of the subnet hosting the VM. You can get the list of available subnets using the yc vpc subnet list CLI command.
     • ip_address: VM internal IP address. You can get the list of internal IP addresses using the following CLI command: yc vpc subnet list-used-addresses --id <subnet_ID>.

   You can also create a target group with resources outside Yandex Virtual Private Cloud, e.g., in your data center connected to Yandex Cloud via Yandex Cloud Interconnect:

   resource "yandex_alb_target_group" "foo" {
     name                   = "<target_group_name>"
   
     target {
       private_ipv4_address = true
       ip_address           = "<resource_1_IPv4_private_address>"
     }
   
     target {
       private_ipv4_address = true
       ip_address           = "<resource_2_IPv4_private_address>"
     }
   
     target {
       private_ipv4_address = true
       ip_address           = "<resource_3_IPv4_private_address>"
     }
   }
   

   Where yandex_alb_target_group specifies target group settings:

   • name: Target group name.
   • target: Target settings:
     • private_ipv4_address: Setting indicating that the IP address is outside Virtual Private Cloud.
     • ip_address: Resource’s private IPv4 address. This IP address must belong to the RFC 1918 private address range. For more information, see Subnets.

   For more information about yandex_alb_target_group properties, see the relevant Terraform article.

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 all the required resources. You can check the new resources in the management console or using this CLI command:

   yc alb target-group list
   

   Timeouts

   The Terraform provider limits operations with Application Load Balancer target groups to 10 minutes.

   Operations in excess of this time will be interrupted.

   How do I modify these limits?

   Add the timeouts section to the target group description, e.g.:

   resource "yandex_alb_target_group" "<target_group_name>" {
     ...
     timeouts {
       create = "60m"
       update = "60m"
       delete = "60m"
     }
   }
   

Use the create REST API method for the TargetGroup resource or the TargetGroupService/Create gRPC API call.