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
          • trino_access_control
          • trino_catalog
          • trino_cluster

In this article:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  • Nested Schema for coordinator
  • Nested Schema for logging
  • Nested Schema for maintenance_window
  • Nested Schema for retry_policy
  • Nested Schema for retry_policy.exchange_manager
  • Nested Schema for retry_policy.exchange_manager.service_s3
  • Nested Schema for tls
  • Nested Schema for worker
  • Nested Schema for worker.auto_scale
  • Nested Schema for worker.fixed_scale
  1. Terraform reference
  2. Resources
  3. Managed Service for Trino
  4. Data Sources
  5. trino_cluster

yandex_trino_cluster (Data Source)

Written by
Yandex Cloud
Updated at October 20, 2025
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for timeouts
    • Nested Schema for coordinator
    • Nested Schema for logging
    • Nested Schema for maintenance_window
    • Nested Schema for retry_policy
    • Nested Schema for retry_policy.exchange_manager
    • Nested Schema for retry_policy.exchange_manager.service_s3
    • Nested Schema for tls
    • Nested Schema for worker
    • Nested Schema for worker.auto_scale
    • Nested Schema for worker.fixed_scale

Managed Trino cluster.

Example usageExample usage

//
// Get information about Trino cluster by name
//
data "yandex_tirno_cluster" "trino_cluster_by_name" {
  name = "trino-created-with-terraform"
}

//
// Get information about Trino cluster by id
//
data "yandex_trino_cluster" "tirno_cluster_by_id" {
  id = "<trino-cluster-id>"
}

SchemaSchema

OptionalOptional

  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • id (String) The resource identifier.
  • name (String) The resource name.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • coordinator (Attributes) Configuration of coordinator instances. (see below for nested schema)
  • created_at (String) The creation timestamp of the resource.
  • deletion_protection (Boolean) The true value means that resource is protected from accidental deletion.
  • description (String) The resource description.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • logging (Attributes) Cloud Logging configuration. (see below for nested schema)
  • maintenance_window (Attributes) Configuration of window for maintenance operations. (see below for nested schema)
  • retry_policy (Attributes) Configuration for retry policy, specifying the spooling storage destination and other settings. (see below for nested schema)
  • security_group_ids (Set of String) The list of security groups applied to resource or their components.
  • service_account_id (String) Service account which linked to the resource. For more information, see documentation.
  • subnet_ids (Set of String) The list of VPC subnets identifiers which resource is attached.
  • tls (Attributes) Configuration for TLS. (see below for nested schema)
  • version (String) Trino version. Format: "Number".
  • worker (Attributes) Configuration of worker instances. (see below for nested schema)

Nested Schema for Nested Schema for timeouts

Optional:

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

Nested Schema for Nested Schema for coordinator

Read-Only:

  • resource_preset_id (String) The identifier of the preset for computational resources available to an instance (CPU, memory etc.).

Nested Schema for Nested Schema for logging

Read-Only:

  • enabled (Boolean) Enables delivery of logs generated by the Trino components to Cloud Logging.
  • folder_id (String) Logs will be written to default log group of specified folder. Exactly one of the attributes folder_id or log_group_id should be specified.
  • log_group_id (String) Logs will be written to the specified log group. Exactly one of the attributes folder_id or log_group_id should be specified.
  • min_level (String) Minimum level of messages that will be sent to Cloud Logging. Can be either TRACE, DEBUG, INFO, WARN, ERROR or FATAL. If not set then server default is applied (currently INFO).

Nested Schema for Nested Schema for maintenance_window

Read-Only:

  • day (String) Day of week for maintenance window. One of MON, TUE, WED, THU, FRI, SAT, SUN.
  • hour (Number) Hour of day in UTC time zone (1-24) for maintenance window.
  • type (String) Type of maintenance window. Can be either ANYTIME or WEEKLY. If WEEKLY, day and hour must be specified.

Nested Schema for Nested Schema for retry_policy

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • exchange_manager (Attributes) Configuration for exchange manager. (see below for nested schema)
  • policy (String) Retry policy level

Nested Schema for Nested Schema for retry_policy.exchange_manager

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • service_s3 (Attributes) Use S3 created on service side as exchange manager. (see below for nested schema)

Nested Schema for Nested Schema for retry_policy.exchange_manager.service_s3

Nested Schema for Nested Schema for tls

Read-Only:

  • trusted_certificates (List of String) Trusted CA-certificates. Each element should contain single self-signed CA-certificate or chain of CA-certificates where first certificate if leaf and last certificate is self-signed root.

Nested Schema for Nested Schema for worker

Read-Only:

  • auto_scale (Attributes) A scaling policy that dynamically adjusts the number of worker instances based on the cluster's workload. (see below for nested schema)
  • fixed_scale (Attributes) A fixed scaling policy that specifies a fixed number of worker instances. (see below for nested schema)
  • resource_preset_id (String) The identifier of the preset for computational resources available to an instance (CPU, memory etc.).

Nested Schema for Nested Schema for worker.auto_scale

Read-Only:

  • max_count (Number) The maximum number of worker instances.
  • min_count (Number) The minimum number of worker instances.

Nested Schema for Nested Schema for worker.fixed_scale

Read-Only:

  • count (Number) Specifies the number of worker instances.

Was the article helpful?

Previous
trino_catalog
Next
trino_access_control
© 2025 Direct Cursus Technology L.L.C.