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
  • Required
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  • Nested Schema for clickhouse
  • Nested Schema for clickhouse.connection_manager
  • Nested Schema for clickhouse.on_premise
  • Nested Schema for delta_lake
  • Nested Schema for delta_lake.file_system
  • Nested Schema for delta_lake.file_system.external_s3
  • Nested Schema for delta_lake.file_system.s3
  • Nested Schema for delta_lake.metastore
  • Nested Schema for hive
  • Nested Schema for hive.file_system
  • Nested Schema for hive.file_system.external_s3
  • Nested Schema for hive.file_system.s3
  • Nested Schema for hive.metastore
  • Nested Schema for hudi
  • Nested Schema for hudi.file_system
  • Nested Schema for hudi.file_system.external_s3
  • Nested Schema for hudi.file_system.s3
  • Nested Schema for hudi.metastore
  • Nested Schema for iceberg
  • Nested Schema for iceberg.file_system
  • Nested Schema for iceberg.file_system.external_s3
  • Nested Schema for iceberg.file_system.s3
  • Nested Schema for iceberg.metastore
  • Nested Schema for oracle
  • Nested Schema for oracle.on_premise
  • Nested Schema for postgresql
  • Nested Schema for postgresql.connection_manager
  • Nested Schema for postgresql.on_premise
  • Nested Schema for sqlserver
  • Nested Schema for sqlserver.on_premise
  • Nested Schema for tpcds
  • Nested Schema for tpch
  1. Terraform reference
  2. Resources
  3. Managed Service for Trino
  4. Data Sources
  5. trino_catalog

yandex_trino_catalog (Data Source)

Written by
Yandex Cloud
Updated at October 20, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for timeouts
    • Nested Schema for clickhouse
    • Nested Schema for clickhouse.connection_manager
    • Nested Schema for clickhouse.on_premise
    • Nested Schema for delta_lake
    • Nested Schema for delta_lake.file_system
    • Nested Schema for delta_lake.file_system.external_s3
    • Nested Schema for delta_lake.file_system.s3
    • Nested Schema for delta_lake.metastore
    • Nested Schema for hive
    • Nested Schema for hive.file_system
    • Nested Schema for hive.file_system.external_s3
    • Nested Schema for hive.file_system.s3
    • Nested Schema for hive.metastore
    • Nested Schema for hudi
    • Nested Schema for hudi.file_system
    • Nested Schema for hudi.file_system.external_s3
    • Nested Schema for hudi.file_system.s3
    • Nested Schema for hudi.metastore
    • Nested Schema for iceberg
    • Nested Schema for iceberg.file_system
    • Nested Schema for iceberg.file_system.external_s3
    • Nested Schema for iceberg.file_system.s3
    • Nested Schema for iceberg.metastore
    • Nested Schema for oracle
    • Nested Schema for oracle.on_premise
    • Nested Schema for postgresql
    • Nested Schema for postgresql.connection_manager
    • Nested Schema for postgresql.on_premise
    • Nested Schema for sqlserver
    • Nested Schema for sqlserver.on_premise
    • Nested Schema for tpcds
    • Nested Schema for tpch

Catalog for Managed Trino cluster.

Example usageExample usage

//
// Get information about Trino catalog by name
//
data "yandex_trino_catalog" "trino_catalog_by_name" {
  cluster_id = yandex_trino_cluster.trino.id
  name       = "catalog"
}

//
// Get information about Trino catalog by id
//
data "yandex_trino_catalog" "trino_catalog_by_id" {
  cluster_id = yandex_trino_cluster.trino.id
  id         = "<tirno-catalog-id>"
}

SchemaSchema

RequiredRequired

  • cluster_id (String) ID of the Trino cluster.

OptionalOptional

  • id (String) The resource identifier.
  • name (String) The resource name.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • clickhouse (Attributes) Configuration for Clickhouse connector. (see below for nested schema)
  • delta_lake (Attributes) Configuration for Delta Lake connector. (see below for nested schema)
  • description (String) The resource description.
  • hive (Attributes) Configuration for Hive connector. (see below for nested schema)
  • hudi (Attributes) Configuration for Hudi connector. (see below for nested schema)
  • iceberg (Attributes) Configuration for Iceberg connector. (see below for nested schema)
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • oracle (Attributes) Configuration for Oracle connector. (see below for nested schema)
  • postgresql (Attributes) Configuration for Postgresql connector. (see below for nested schema)
  • sqlserver (Attributes) Configuration for SQLServer connector. (see below for nested schema)
  • tpcds (Attributes) Configuration for TPCDS connector. (see below for nested schema)
  • tpch (Attributes) Configuration for TPCH connector. (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 clickhouse

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • connection_manager (Attributes) Configuration for connection manager connection. (see below for nested schema)
  • on_premise (Attributes) Configuration for on-premise connection. (see below for nested schema)

Nested Schema for Nested Schema for clickhouse.connection_manager

Read-Only:

  • connection_id (String) Connection ID.
  • connection_properties (Map of String) Additional connection properties.
  • database (String) Database.

Nested Schema for Nested Schema for clickhouse.on_premise

Read-Only:

  • connection_url (String) Connection URL.
  • password (String, Sensitive) Password of the user.
  • user_name (String) Name of the user.

Nested Schema for Nested Schema for delta_lake

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • file_system (Attributes) File system configuration. (see below for nested schema)
  • metastore (Attributes) Metastore configuration. (see below for nested schema)

Nested Schema for Nested Schema for delta_lake.file_system

Read-Only:

  • external_s3 (Attributes) Describes External S3 compatible file system. (see below for nested schema)
  • s3 (Attributes) Describes YandexCloud native S3 file system. (see below for nested schema)

Nested Schema for Nested Schema for delta_lake.file_system.external_s3

Read-Only:

  • aws_access_key (String, Sensitive) AWS access key ID for S3 authentication.
  • aws_endpoint (String) AWS S3 compatible endpoint URL.
  • aws_region (String) AWS region for S3 storage.
  • aws_secret_key (String, Sensitive) AWS secret access key for S3 authentication.

Nested Schema for Nested Schema for delta_lake.file_system.s3

Nested Schema for Nested Schema for delta_lake.metastore

Read-Only:

  • uri (String) The resource description.

Nested Schema for Nested Schema for hive

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • file_system (Attributes) File system configuration. (see below for nested schema)
  • metastore (Attributes) Metastore configuration. (see below for nested schema)

Nested Schema for Nested Schema for hive.file_system

Read-Only:

  • external_s3 (Attributes) Describes External S3 compatible file system. (see below for nested schema)
  • s3 (Attributes) Describes YandexCloud native S3 file system. (see below for nested schema)

Nested Schema for Nested Schema for hive.file_system.external_s3

Read-Only:

  • aws_access_key (String, Sensitive) AWS access key ID for S3 authentication.
  • aws_endpoint (String) AWS S3 compatible endpoint URL.
  • aws_region (String) AWS region for S3 storage.
  • aws_secret_key (String, Sensitive) AWS secret access key for S3 authentication.

Nested Schema for Nested Schema for hive.file_system.s3

Nested Schema for Nested Schema for hive.metastore

Read-Only:

  • uri (String) The resource description.

Nested Schema for Nested Schema for hudi

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • file_system (Attributes) File system configuration. (see below for nested schema)
  • metastore (Attributes) Metastore configuration. (see below for nested schema)

Nested Schema for Nested Schema for hudi.file_system

Read-Only:

  • external_s3 (Attributes) Describes External S3 compatible file system. (see below for nested schema)
  • s3 (Attributes) Describes YandexCloud native S3 file system. (see below for nested schema)

Nested Schema for Nested Schema for hudi.file_system.external_s3

Read-Only:

  • aws_access_key (String, Sensitive) AWS access key ID for S3 authentication.
  • aws_endpoint (String) AWS S3 compatible endpoint URL.
  • aws_region (String) AWS region for S3 storage.
  • aws_secret_key (String, Sensitive) AWS secret access key for S3 authentication.

Nested Schema for Nested Schema for hudi.file_system.s3

Nested Schema for Nested Schema for hudi.metastore

Read-Only:

  • uri (String) The resource description.

Nested Schema for Nested Schema for iceberg

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • file_system (Attributes) File system configuration. (see below for nested schema)
  • metastore (Attributes) Metastore configuration. (see below for nested schema)

Nested Schema for Nested Schema for iceberg.file_system

Read-Only:

  • external_s3 (Attributes) Describes External S3 compatible file system. (see below for nested schema)
  • s3 (Attributes) Describes YandexCloud native S3 file system. (see below for nested schema)

Nested Schema for Nested Schema for iceberg.file_system.external_s3

Read-Only:

  • aws_access_key (String, Sensitive) AWS access key ID for S3 authentication.
  • aws_endpoint (String) AWS S3 compatible endpoint URL.
  • aws_region (String) AWS region for S3 storage.
  • aws_secret_key (String, Sensitive) AWS secret access key for S3 authentication.

Nested Schema for Nested Schema for iceberg.file_system.s3

Nested Schema for Nested Schema for iceberg.metastore

Read-Only:

  • uri (String) The resource description.

Nested Schema for Nested Schema for oracle

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • on_premise (Attributes) Configuration for on-premise connection. (see below for nested schema)

Nested Schema for Nested Schema for oracle.on_premise

Read-Only:

  • connection_url (String) Connection URL.
  • password (String, Sensitive) Password of the user.
  • user_name (String) Name of the user.

Nested Schema for Nested Schema for postgresql

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • connection_manager (Attributes) Configuration for connection manager connection. (see below for nested schema)
  • on_premise (Attributes) Configuration for on-premise connection. (see below for nested schema)

Nested Schema for Nested Schema for postgresql.connection_manager

Read-Only:

  • connection_id (String) Connection ID.
  • connection_properties (Map of String) Additional connection properties.
  • database (String) Database.

Nested Schema for Nested Schema for postgresql.on_premise

Read-Only:

  • connection_url (String) Connection URL.
  • password (String, Sensitive) Password of the user.
  • user_name (String) Name of the user.

Nested Schema for Nested Schema for sqlserver

Read-Only:

  • additional_properties (Map of String) Additional properties.
  • on_premise (Attributes) Configuration for on-premise connection. (see below for nested schema)

Nested Schema for Nested Schema for sqlserver.on_premise

Read-Only:

  • connection_url (String) Connection URL.
  • password (String, Sensitive) Password of the user.
  • user_name (String) Name of the user.

Nested Schema for Nested Schema for tpcds

Read-Only:

  • additional_properties (Map of String) Additional properties.

Nested Schema for Nested Schema for tpch

Read-Only:

  • additional_properties (Map of String) Additional properties.

Was the article helpful?

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