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
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Serverless Containers
  • Comparison with other Yandex Cloud services
    • Overview
    • Container
    • Invoking a container
    • Runtime environment
    • Networking
    • Mounting external resources to a container file system
    • Long-lived containers
    • Container termination notifications
      • Overview
      • Timer
      • Trigger for Message Queue
      • Trigger for Object Storage
      • Trigger for Container Registry
      • Trigger for Yandex Cloud Logging
      • Trigger for Yandex IoT Core
      • Trigger for budgets
      • Trigger for Data Streams
      • Email trigger
    • Dead Letter Queue
    • Container logs
    • Backups
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Roles required for the proper operation of a trigger for Data Streams
  • Format of the message from the trigger for Data Streams
  • See also
  1. Concepts
  2. Trigger
  3. Trigger for Data Streams

Trigger for Data Streams that invokes a Serverless Containers container

Written by
Yandex Cloud
Updated at December 20, 2024
  • Roles required for the proper operation of a trigger for Data Streams
  • Format of the message from the trigger for Data Streams
  • See also

Trigger for Data Streams calls a Serverless Containers container when data is sent to a stream.

A trigger for Data Streams needs service accounts to manage a stream and invoke a container. You can use the same service account for both operations.

For more information about creating a trigger for Data Streams, see Creating a trigger for Data Streams that invokes a Serverless Containers container.

Roles required for the proper operation of a trigger for Data StreamsRoles required for the proper operation of a trigger for Data Streams

  • To create a trigger, you need a permission for the service account under which the trigger executes the operation. This permission comes with the iam.serviceAccounts.user and editor roles or higher.
  • For the trigger to fire, service accounts need the following roles:
    • serverless.containers.invoker for the container the trigger invokes.
    • yds.admin for the stream that invokes the trigger when data is sent there.

Format of the message from the trigger for Data StreamsFormat of the message from the trigger for Data Streams

The trigger for Data Streams accepts and sends messages in JSON format only.

Once the trigger fires, it will send a message with the messages array to the container:

{
   "messages":[
      {
         "key1":"value1"
      },
      {
         "key2":"value2"
      }
   ]
}

See alsoSee also

  • Trigger for Data Streams that invokes a Cloud Functions function
  • Trigger for Data Streams that sends messages to WebSocket connections

Was the article helpful?

Previous
Trigger for budgets
Next
Email trigger
© 2025 Direct Cursus Technology L.L.C.