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

In this article:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  • Nested Schema for code_sync
  • Nested Schema for code_sync.s3
  • Nested Schema for dag_processor
  • Nested Schema for lockbox_secrets_backend
  • Nested Schema for logging
  • Nested Schema for maintenance_window
  • Nested Schema for scheduler
  • Nested Schema for triggerer
  • Nested Schema for webserver
  • Nested Schema for worker
  1. Terraform reference
  2. Resources
  3. Managed Service for Apache Airflow
  4. Data Sources
  5. airflow_cluster

yandex_airflow_cluster (Data Source)

Written by
Yandex Cloud
Updated at November 17, 2025
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for timeouts
    • Nested Schema for code_sync
    • Nested Schema for code_sync.s3
    • Nested Schema for dag_processor
    • Nested Schema for lockbox_secrets_backend
    • Nested Schema for logging
    • Nested Schema for maintenance_window
    • Nested Schema for scheduler
    • Nested Schema for triggerer
    • Nested Schema for webserver
    • Nested Schema for worker

Managed Airflow cluster.

Example usageExample usage

//
// Get information about Apache Airflow cluster by name
//
data "yandex_airflow_cluster" "airflow_cluster_by_name" {
  name = "airflow-created-with-terraform"
}

//
// Get information about Apache Airflow cluster by id
//
data "yandex_airflow_cluster" "airflow_cluster_by_id" {
  id = "<airflow-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. Exactly one of the attributes id or name should be specified.
  • name (String) The resource name. Exactly one of the attributes id or name should be specified.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • admin_password (String, Sensitive) Password that is used to log in to Apache Airflow web UI under admin user.
  • airflow_config (Map of Map of String) Configuration of the Apache Airflow application itself. The value of this attribute is a two-level map. Keys of top-level map are the names of configuration sections. Keys of inner maps are the names of configuration options within corresponding section.
  • airflow_version (String) Apache Airflow version in format <major>.<minor>.
  • code_sync (Attributes) Parameters of the location and access to the code that will be executed in the cluster. (see below for nested schema)
  • created_at (String) The creation timestamp of the resource.
  • dag_processor (Attributes) Configuration of dag-processor instances. (see below for nested schema)
  • deb_packages (Set of String) System packages that are installed in the cluster.
  • 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.
  • lockbox_secrets_backend (Attributes) Configuration of Lockbox Secrets Backend. See documentation for details. (see below for nested schema)
  • logging (Attributes) Cloud Logging configuration. (see below for nested schema)
  • maintenance_window (Attributes) Configuration of window for maintenance operations. (see below for nested schema)
  • pip_packages (Set of String) Python packages that are installed in the cluster.
  • python_version (String) Version of Python that Airflow will run on. Must be in format <major>.<minor>.
  • scheduler (Attributes) Configuration of scheduler instances. (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.
  • status (String) Status of the cluster. Can be either CREATING, STARTING, RUNNING, UPDATING, STOPPING, STOPPED, ERROR or STATUS_UNKNOWN. For more information see status field of JSON representation in the official documentation.
  • subnet_ids (Set of String) The list of VPC subnets identifiers which resource is attached.
  • triggerer (Attributes) Configuration of triggerer instances. (see below for nested schema)
  • webserver (Attributes) Configuration of webserver instances. (see below for nested schema)
  • 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 code_sync

Read-Only:

  • s3 (Attributes) Currently only Object Storage (S3) is supported as the source of DAG files. (see below for nested schema)

Nested Schema for Nested Schema for code_sync.s3

Read-Only:

  • bucket (String) The name of the Object Storage bucket that stores DAG files used in the cluster.

Nested Schema for Nested Schema for dag_processor

Read-Only:

  • count (Number) The number of dag-processor instances in the cluster.
  • 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 lockbox_secrets_backend

Read-Only:

  • enabled (Boolean) Enables usage of Lockbox Secrets Backend.

Nested Schema for Nested Schema for logging

Read-Only:

  • enabled (Boolean) Enables delivery of logs generated by the Airflow components to Cloud Logging.
  • folder_id (String) Logs are written to default log group of specified folder.
  • log_group_id (String) Logs are written to the specified log group.
  • min_level (String) Minimum level of messages that are sent to Cloud Logging. Can be either TRACE, DEBUG, INFO, WARN, ERROR or FATAL.

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 scheduler

Read-Only:

  • count (Number) The number of scheduler instances in the cluster.
  • 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 triggerer

Read-Only:

  • count (Number) The number of triggerer instances in the cluster.
  • 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 webserver

Read-Only:

  • count (Number) The number of webserver instances in the cluster.
  • 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

Read-Only:

  • max_count (Number) The maximum number of worker instances in the cluster.
  • min_count (Number) The minimum number of worker instances in the cluster.
  • resource_preset_id (String) The identifier of the preset for computational resources available to an instance (CPU, memory etc.).

Was the article helpful?

Previous
kubernetes_marketplace_helm_release
Next
airflow_cluster
© 2025 Direct Cursus Technology L.L.C.