Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Serverless Containers
  • Comparison with other Yandex Cloud services
    • All guides
    • Getting an IAM token for a service account using a container
      • Creating a timer
      • Creating a trigger for Message Queue
      • Creating a trigger for Object Storage
      • Creating a trigger for Container Registry
      • Creating a trigger for Cloud Logging
      • Creating a trigger for budgets
      • Creating a trigger for Data Streams
      • Creating an email trigger
    • Viewing operations with service resources
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Getting started
  • Creating a trigger
  • Checking the result
  • See also
  1. Step-by-step guides
  2. Creating a trigger
  3. Creating a trigger for budgets

Creating a trigger for budgets that invokes a Serverless Containers container

Written by
Yandex Cloud
Updated at May 13, 2025
  • Getting started
  • Creating a trigger
  • Checking the result
  • See also

Create a trigger for budgets that invokes a Serverless Containers container when threshold values are exceeded.

Getting started

To create a trigger, you will need:

  • A container that the trigger will invoke. If you do not have a container:

    • Create a container.
    • Create a container revision.
  • Optionally, a dead letter queue where messages that could not be processed by a container will be redirected. If you do not have a queue, create one.

  • Service account with rights to invoke the container and (optionally) write messages to the dead letter queue. You can use the same service account or different ones. If you do not have a service account, create one.

  • A budget which, when exceeded, fires a trigger. If you do not have a budget, create one.

Creating a trigger

Note

The trigger is initiated within 5 minutes of being created.

Management console
CLI
API
  1. In the management console, select the folder you want to create a trigger in.

  2. Open Serverless Containers.

  3. In the left-hand panel, select Triggers.

  4. Click Create trigger.

  5. Under Basic settings:

    • Enter a name and description for the trigger.
    • In the Type field, select Budget.
    • In the Launched resource field, select Container.
  6. Under Budget settings, select your billing account and budget. You can select Any budget.

  7. Under Container settings, select a container and specify a service account to invoke it under.

  8. Optionally, under Repeat request settings:

    • In the Interval field, specify the time interval to retry invoking the container if the current attempt fails. The values may range from 10 to 60 seconds. The default value is 10 seconds.
    • In the Number of attempts field, specify the number of invocation retries before the trigger moves a message to the dead letter queue. The values may range from 1 to 5. The default value is 1.
  9. Optionally, under Dead Letter Queue settings, select the dead-letter queue and the service account with write permissions for this queue.

  10. Click Create trigger.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

To create a trigger that invokes a container, run this command:

yc serverless trigger create billing-budget \
  --name <trigger_name> \
  --billing-account-id <billing_account_ID> \
  --budget-id <budget_ID> \
  --invoke-container-id <container_ID> \
  --invoke-container-service-account-id <service_account_ID> \
  --retry-attempts 1 \
  --retry-interval 10s \
  --dlq-queue-id <dead-letter_queue_ID> \
  --dlq-service-account-id <service_account_ID>

Where:

  • --name: Trigger name.
  • --billing-account-id: Billing account ID.
  • --budget-id: Budget ID.
  • --invoke-container-id: Container ID.
  • --invoke-container-service-account-id: ID of the service account with permissions 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-interval: 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-queue-id: Dead-letter queue ID. This is an optional parameter.
  • --dlq-service-account-id: ID of the service account with write permissions to the dead-letter queue. This is an optional parameter.

Result:

id: a1sfe084v4h2********
folder_id: b1g88tflruh2********
created_at: "2019-12-04T08:45:31.131391Z"
name: budget-trigger
rule:
  billing-budget:
    billing-account-id: dn2char50jh2********
    budget-id: dn2jnshmdlh2********
    invoke_container:
      container_id: d4eofc7n0mh2********
      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

To create a trigger for budgets, use the create REST API method for the Trigger resource or the TriggerService/Create gRPC API call.

Checking the result

Make sure the trigger is working properly. To do this, view container logs that show information about invocations.

See also

  • Creating a trigger for budgets that invokes a Cloud Functions function
  • Creating a trigger for budgets that sends messages to WebSocket connections

Was the article helpful?

Previous
Broker
Next
Creating a trigger for Data Streams
Yandex project
© 2025 Yandex.Cloud LLC