Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML Services
    • 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
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Serverless Containers
  • Comparison with other Yandex Cloud services
    • All guides
    • Getting an IAM token for a service account using a container
      • Updating a trigger
      • Viewing monitoring charts
      • Deleting a trigger
    • Viewing operations with service resources
  • Access management
  • Tools
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ
  1. Step-by-step guides
  2. Managing a trigger
  3. Updating a trigger

Updating a trigger in Serverless Containers

Written by
Yandex Cloud
Improved by
Danila N.
Updated at July 29, 2025

You can update any parameters except for the trigger type and launched resource type.

Note

Your changes will apply within five minutes.

Management console
CLI
Terraform
API
  1. In the management console, select the folder containing your trigger.
  2. Open Serverless Containers.
  3. In the left-hand panel, select Triggers.
  4. Select the trigger whose parameters you want to update.
  5. In the top-right corner of the page, click Edit.
  6. Edit the trigger parameters and click Save.

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.

To find out the name or unique ID of a trigger, get a list of triggers in the folder.

  1. See the description of the CLI command for updating trigger parameters:

    yc serverless trigger update <trigger_type> --help
    
  2. Update the trigger parameters, e.g., rename it:

    yc serverless trigger update <trigger_type> <trigger_name> \
      --new-name <new_trigger_name> 
    

    Result:

    id: a1s5msktijh2********
    folder_id: b1gmit33hgh2********
    created_at: "2022-10-24T15:19:15.353909857Z"
    name: my-trigger
    rule:
      object_storage:
        event_type:
        - OBJECT_STORAGE_EVENT_TYPE_CREATE_OBJECT
        - OBJECT_STORAGE_EVENT_TYPE_DELETE_OBJECT
        - OBJECT_STORAGE_EVENT_TYPE_UPDATE_OBJECT
        bucket_id: s3-for-trigger
        prefix: dev
        suffix: 12.jpg
        invoke_container:
          container_id: bba5jb38o8h2********
          service_account_id: aje3932acdh2********
          retry_settings:
            retry_attempts: "1"
            interval: 10s
          dead_letter_queue:
            queue-id: yrn:yc:ymq:ru-central1:aoek49ghmkh2********:dlq
            service-account-id: aje3932acdh2********
    status: ACTIVE
    

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. Open the Terraform configuration file and update the parameters of the function_trigger resource:

    resource "yandex_function_trigger" "my_trigger" {
      name        = "<timer_name>"
      timer {
        cron_expression = "<cron_expression>"
        payload         = "<message>"
      }
      container {
        id                 = "<container_ID>"
        service_account_id = "<service_account_ID>"
        retry_attempts     = <number_of_retry_attempts>
        retry_interval     = <time_between_retry_attempts>
      }
      dlq {
        queue_id           = "<dead-letter_queue_ID>"
        service_account_id = "<service_account_ID>"
      }
    }
    

    Where:

    • name: Timer name. The name format is as follows:

      • It must be from 2 to 63 characters long.
      • It can only contain lowercase Latin letters, numbers, and hyphens.
      • It must start with a letter and cannot end with a hyphen.
    • timer: Trigger parameters:

      • cron_expression: Container invocation schedule specified as a cron expression.
      • payload: Message that will be sent to the function if the timer fires. The string length must not exceed 4,096 characters.
    • container: Settings for the container that will be activated by the trigger:

      • id: Container ID.
      • service_account_id: ID of the service account with rights to invoke the container.
      • retry_attempts: Number of invocation retries before the trigger moves a message to the dead letter queue. This is an optional parameter. The values may range from 1 to 5. The default value is 1.
      • retry_intervall: Time to retry invoking the container if the current attempt fails. This is an optional parameter. The values may range from 10 to 60 seconds. The default value is 10 seconds.
    • dlq: Dead-letter queue message parameters:
      • queue_id: Dead-letter queue ID. This is an optional parameter.
      • service_account_id: ID of the service account with write permissions to the dead-letter queue. This is an optional parameter.

    For more information about the function_trigger resource parameters, see the relevant provider documentation.

  2. Create 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.

    You can check the updates using the management console or this CLI command:

    yc serverless trigger list
    

To update parameters of a trigger, use the update REST API method for the Trigger resource or the TriggerService/Update gRPC API call.

Was the article helpful?

Previous
Creating an email trigger
Next
Viewing monitoring charts
© 2025 Direct Cursus Technology L.L.C.