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
          • iot_core_broker
          • iot_core_device
          • iot_core_registry

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for log_options
  • Nested Schema for timeouts
  • Import
  1. Terraform reference
  2. Resources
  3. IoT Core
  4. Resources
  5. iot_core_broker

yandex_iot_core_broker (Resource)

Written by
Yandex Cloud
Updated at September 11, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for log_options
    • Nested Schema for timeouts
  • Import

Allows management of Yandex Cloud IoT Broker.

Example usageExample usage

//
// Create a new IoT Core Broker.
//
resource "yandex_iot_core_broker" "my_broker" {
  name        = "some_name"
  description = "any description"
  labels = {
    my-label = "my-label-value"
  }
  log_options {
    log_group_id = "log-group-id"
    min_level    = "ERROR"
  }
  certificates = [
    "public part of certificate1",
    "public part of certificate2"
  ]
}

SchemaSchema

RequiredRequired

  • name (String) The resource name.

OptionalOptional

  • certificates (Set of String) A set of certificate's fingerprints for the IoT Core Broker.
  • description (String) The resource description.
  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • log_options (Block List, Max: 1) Options for logging for IoT Core Broker. (see below for nested schema)
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • id (String) The ID of this resource.

Nested Schema for Nested Schema for log_options

Optional:

  • disabled (Boolean) Is logging for broker disabled.
  • folder_id (String) Log entries are written to default log group for specified folder.
  • log_group_id (String) Log entries are written to specified log group.
  • min_level (String) Minimum log entry level.

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).
  • 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.
  • 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

Warning

Import for this resource is not implemented yet.

Was the article helpful?

Previous
iot_core_registry
Next
iot_core_device
© 2025 Direct Cursus Technology L.L.C.