[Yandex Cloud documentation](../../../../index.md) > [Yandex Serverless Integrations](../../../index.md) > [Step-by-step guides](../../index.md) > EventRouter > Managing a rule > Managing targets > Updating a target

# Updating a target

{% list tabs group=instructions %}

- Management console {#console}

  1. In the [management console](https://console.yandex.cloud), go to the folder where you want to update a [target](../../../concepts/eventrouter/rule.md#target).
  1. Navigate to **Serverless Integrations**.
  1. In the left-hand panel, click ![image](../../../../_assets/console-icons/object-align-center-vertical.svg) **EventRouter**.
  1. Select the [bus](../../../concepts/eventrouter/bus.md) you need.
  1. Navigate to the ![image](../../../../_assets/console-icons/target-dart.svg) **Rules** tab.
  1. In the [rule](../../../concepts/eventrouter/rule.md) row, click ![image](../../../../_assets/console-icons/ellipsis.svg) and select ![image](../../../../_assets/console-icons/pencil.svg) **Edit**.
  1. Edit the target parameters.
  1. Click **Save**.

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../../../cli/quickstart.md#install).

  The folder used by default is the one specified when [creating](../../../../cli/operations/profile/profile-create.md) 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.

  To update a [target](../../../concepts/eventrouter/rule.md#target) in a [rule](../../../concepts/eventrouter/rule.md), run the following command, specifying the name or the ID of the rule and a list of targets with parameters:

  {% note warning %}
  
  The existing targets will be completely overwritten by the ones you provide in your request.
  
  {% endnote %}
  
  ```bash
  yc serverless eventrouter rule update <rule_name_or_ID> \
    --target_1 <parameter_1>=<value_1>,...,<parameter_N>=<value_N> \
    --target_2 <parameter_1>=<value_1>,...,<parameter_N>=<value_N> \
    ...
    --target_N <parameter_1>=<value_1>,...,<parameter_N>=<value_N>
  ```

  Example of a command with three targets:
  
  ```bash
  yc serverless eventrouter rule update my-rule \
    --logging-target log-group-id=e23di6hvn5fm********,service-account-id=ajelprpohp7r******** \
    --workflow-target workflow-id=dfq28ndgtojl********,service-account-id=ajelprpohp7r******** \
    --function-target function-id=d4e27bc01uu7********,function-tag=$latest,service-account-id=ajelprpohp7r********
  ```
  
  Result:
  
  ```text
  id: f66h4vmpsvoh********
  bus_id: f66epjc9llqt********
  folder_id: b1g681qpemb4********
  cloud_id: b1gia87mbaom********
  created_at: "2025-03-02T07:57:22.064950Z"
  name: my-rule
  targets:
    - function:
        function_id: d4e27bc01uu7********
        service_account_id: oielprnahp7r********
        batch_settings:
          max_count: "1"
          max_bytes: "10000"
          cutoff: 60s
      retry_settings:
        retry_attempts: "3"
        maximum_age: 600s
      status: ENABLED
    - logging:
        log_group_id: e23di6hvn5fm********
        service_account_id: aj91prpohp6q********
      retry_settings:
        retry_attempts: "3"
        maximum_age: 600s
      status: ENABLED
    - workflow:
        workflow_id: dfq28ndgtojl********
        service_account_id: ajel4bnehp5s********
        batch_settings:
          max_count: "1"
          max_bytes: "10000"
          cutoff: 60s
      retry_settings:
        retry_attempts: "3"
        maximum_age: 600s
      status: ENABLED
  status: ENABLED
  ```

- Terraform {#tf}

  With [Terraform](https://www.terraform.io/), 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](https://github.com/hashicorp/terraform/blob/main/LICENSE). The [Yandex Cloud provider for Terraform](https://github.com/yandex-cloud/terraform-provider-yandex) is distributed under the [MPL-2.0](https://www.mozilla.org/en-US/MPL/2.0/) license.
  
  For more information about the provider resources, see the guides on the [Terraform](https://www.terraform.io/docs/providers/yandex/index.html) website or [its mirror](../../../../terraform/index.md).

  If you do not have Terraform yet, [install it and configure the Yandex Cloud provider](../../../../tutorials/infrastructure-management/terraform-quickstart.md#install-terraform).
  
  
  To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), [authenticate](../../../../terraform/authentication.md) using the appropriate method.

  To update a [target](../../../concepts/eventrouter/rule.md#target) in a [rule](../../../concepts/eventrouter/rule.md):

  1. Open the Terraform configuration file and edit the fragments describing the targets of interest.

      Example of a rule description in the Terraform configuration file:

      ```hcl
      resource "yandex_serverless_eventrouter_rule" "example_rule" {
        bus_id    = "<bus_ID>"
        jq_filter = "<jq_template>"

        ymq {
          queue_arn            = "<queue_ARN>"
          service_account_id   = "<service_account_ID>"
        }

        workflow {
          workflow_id        = "<workflow_ID>"
          service_account_id = "<service_account_ID>"
        }

        yds {
          database           = "<path_to_database>"
          stream_name        = "<data_stream_name>"
          service_account_id = "<service_account_ID>"
        }

        name        = "<rule_name>"
        description = "<rule_description>"

        labels = {
          <key_1> = "<value_1>"
          <key_2> = "<value_2>"
          ...
          <key_n> = "<value_n>"
        }
      }
      ```

      For more on the properties of the `yandex_serverless_eventrouter_rule` resource, see [this provider guide](../../../../terraform/resources/serverless_eventrouter_rule.md).

  1. Apply the changes:

      1. In the terminal, navigate to the configuration file directory.
      1. Make sure the configuration is correct using this command:
      
         ```bash
         terraform validate
         ```
      
         If the configuration is valid, you will get this message:
      
         ```bash
         Success! The configuration is valid.
         ```
      
      1. Run this command:
      
         ```bash
         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.
      1. Apply the configuration changes:
      
         ```bash
         terraform apply
         ```
      
      1. Type `yes` and press **Enter** to confirm the changes.

      Terraform will create all the required resources. You can check the updates using the [management console](https://console.yandex.cloud) or this [CLI](../../../../cli/index.md) command:

      ```bash
      yc serverless eventrouter rule list
      ```

- API {#api}

  To update a [target](../../../concepts/eventrouter/rule.md#target) in a [rule](../../../concepts/eventrouter/rule.md), use the [Update](../../../eventrouter/api-ref/Rule/update.md) REST API method for the [Rule](../../../eventrouter/api-ref/Rule/index.md) resource or the [Rule/Update](../../../eventrouter/api-ref/grpc/Rule/update.md) API call.

{% endlist %}