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
    • AI for business
    • 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.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • serverless_eventrouter_bus
          • serverless_eventrouter_connector
          • serverless_eventrouter_rule

In this article:

  • Example Usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for container
  • Nested Schema for function
  • Nested Schema for function.batch_settings
  • Nested Schema for gateway_websocket_broadcast
  • Nested Schema for logging
  • Nested Schema for workflow
  • Nested Schema for yds
  • Nested Schema for ymq
  1. Terraform reference
  2. Resources
  3. Serverless Integrations
  4. Data Sources
  5. serverless_eventrouter_rule

yandex_serverless_eventrouter_rule (Data Source)

Written by
Yandex Cloud
Updated at August 7, 2025
  • Example Usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for container
    • Nested Schema for function
    • Nested Schema for function.batch_settings
    • Nested Schema for gateway_websocket_broadcast
    • Nested Schema for logging
    • Nested Schema for workflow
    • Nested Schema for yds
    • Nested Schema for ymq

Get information about Serverless Event Router Rule.

Example UsageExample Usage

//
// TBD
//

SchemaSchema

OptionalOptional

  • name (String) Name of the rule
  • rule_id (String) ID of the bus that the rule belongs to

Read-OnlyRead-Only

  • bus_id (String) ID of the bus that the rule belongs to
  • cloud_id (String) ID of the cloud that the rule resides in
  • container (List of Object) ContainerTarget (see below for nested schema)
  • created_at (String) Creation timestamp
  • deletion_protection (Boolean) Deletion protection
  • description (String) Description of the rule
  • folder_id (String) ID of the folder that the rule resides in
  • function (List of Object) FunctionTarget (see below for nested schema)
  • gateway_websocket_broadcast (List of Object) GatewayWebsocketBroadcastTarget (see below for nested schema)
  • id (String) The ID of this resource.
  • jq_filter (String) JQ filter for matching events
  • labels (Map of String) Rule labels
  • logging (List of Object) LoggingTarget. Includes either log_group_id or folder_id (see below for nested schema)
  • workflow (List of Object) WorkflowTarget (see below for nested schema)
  • yds (List of Object) YdsTarget (see below for nested schema)
  • ymq (List of Object) YmqTarget (see below for nested schema)

Nested Schema for Nested Schema for container

Read-Only:

  • batch_settings (String) Batch settings

  • container_id (String) Container ID

  • container_revision_id (String) Container revision ID

  • path (String) Endpoint HTTP path to invoke

  • service_account_id (String) Service account which should be used to call a container

Nested Schema for Nested Schema for function

Read-Only:

  • batch_settings (Block List, Max: 1) Batch settings (see below for nested schema)

  • function_id (String) Function ID

  • function_tag (String) Function tag

  • service_account_id (String) Service account which has call permission on the function

Nested Schema for Nested Schema for function.batch_settings

Read-Only:

  • cutoff (String) Maximum batch size: rule will send a batch if its lifetime exceeds this value

  • max_bytes (Number) Maximum batch size: rule will send a batch if total size of events exceeds this value

  • max_count (Number) Maximum batch size: rule will send a batch if number of events exceeds this value

Nested Schema for Nested Schema for gateway_websocket_broadcast

Read-Only:

  • batch_settings (String) Batch settings

  • gateway_id (String) Gateway ID

  • path (String) Path

  • service_account_id (String) Service account which has permission for writing to websockets

Nested Schema for Nested Schema for logging

Read-Only:

  • folder_id (String) Folder ID

  • log_group_id (String) Log group ID

  • service_account_id (String) Service account which has permission for writing logs

Nested Schema for Nested Schema for workflow

Read-Only:

  • batch_settings (String) Batch settings

  • service_account_id (String) Service account which should be used to start workflow

  • workflow_id (String) Workflow ID

Nested Schema for Nested Schema for yds

Read-Only:

  • database (String) Stream database

  • service_account_id (String) Service account, which has write permission on the stream

  • stream_name (String) Full stream name, like /ru-central1/aoegtvhtp8ob********/cc8004q4lbo6********/test

Nested Schema for Nested Schema for ymq

Read-Only:

  • queue_arn (String) Queue ARN. Example: yrn:yc:ymq:ru-central1:aoe***:test

  • service_account_id (String) Service account which has write access to the queue

Was the article helpful?

Previous
serverless_eventrouter_connector
Next
serverless_eventrouter_bus
© 2025 Direct Cursus Technology L.L.C.