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 timeouts
  • Import
  1. Terraform reference
  2. Resources
  3. Serverless Integrations
  4. Resources
  5. serverless_eventrouter_bus

yandex_serverless_eventrouter_bus (Resource)

Written by
Yandex Cloud
Updated at October 2, 2025
  • Example Usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for timeouts
  • Import

Allows management of a Yandex Cloud Serverless Event Router Bus.

Example UsageExample Usage

//
// TBD
//

SchemaSchema

OptionalOptional

  • bus_id (String) ID of the bus to get.
  • cloud_id (String) ID of the cloud that the bus resides in.
  • deletion_protection (Boolean) Deletion protection.
  • description (String) Description of the bus.
  • folder_id (String) ID of the folder that the bus belongs to.
  • id (String) ID of the bus to get.
  • labels (Map of String) Resource labels as key:value pairs.
  • name (String) Name of the bus.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • created_at (String) Creation timestamp.
  • status (String) Status of the bus.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • read (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
  • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

ImportImport

The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console or YC CLI.

# terraform import yandex_serverless_eventrouter_bus.<resource Name> <resource Id>
terraform import yandex_serverless_eventrouter_bus.evr_bus ...

Was the article helpful?

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