[Документация Yandex Cloud](../../index.md) > [Terraform в Yandex Cloud](../index.md) > Справочник Terraform > Ресурсы (англ.) > Managed Service for Hive Metastore™ > Data Sources > metastore_cluster

# yandex_metastore_cluster (DataSource)

Managed Metastore cluster.

## Example usage

```terraform
//
// Get information about Metastore Cluster by name
//
data "yandex_metastore_cluster" "metastore_cluster_by_name" {
  name = "metastore-created-with-terraform"
}

//
// Get information about Metastore Cluster by id
//
data "yandex_metastore_cluster" "metastore_cluster_by_id" {
  id = "<metastore-cluster-id>"
}
```

## Arguments & Attributes Reference

- `cluster_config` [Block]. Hive Metastore cluster configuration.
  - `resource_preset_id` (**Required**)(String). The identifier of the preset for computational resources available to an instance (CPU, memory etc.).
  - `warehouse_config` [Block]. Warehouse configuration for Hive Metastore. Required for HMS version 4.2+.
    - `s3` [Block]. S3-compatible storage configuration for warehouse.
      - `bucket` (**Required**)(String). Name of the S3 bucket used as warehouse storage.
      - `path` (String). Path prefix within the bucket for warehouse data.
- `created_at` (*Read-Only*) (String). The creation timestamp of the resource.
- `deletion_protection` (Bool). The `true` value means that resource is protected from accidental deletion. By default is set to `false`.
- `description` (String). The resource description.
- `endpoint_ip` (*Read-Only*) (String). IP address of Metastore server balancer endpoint.
- `folder_id` (String). The folder identifier that resource belongs to. If it is not provided, the default provider `folder-id` is used.
- `id` (*Read-Only*) (String). The resource identifier.
- `labels` (Map Of String). A set of key/value label pairs which assigned to resource.
- `logging` [Block]. Cloud Logging configuration.
  - `enabled` (**Required**)(Bool). Enables delivery of logs generated by Metastore to [Cloud Logging](../../logging/index.md).
  - `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`).
- `maintenance_window` [Block]. Configuration of window for maintenance operations.
  - `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.
- `name` (**Required**)(String). The resource name.
- `network_id` (*Read-Only*) (String). VPC network identifier which resource is attached.
- `security_group_ids` (Set Of String). The list of security groups applied to resource or their components.
- `service_account_id` (**Required**)(String). [Service account](../../iam/concepts/users/service-accounts.md) with role `managed-metastore.integrationProvider`. For more information, see [documentation](../../metadata-hub/concepts/metastore-impersonation.md).
- `status` (*Read-Only*) (String). Status of the cluster. Can be either `CREATING`, `STARTING`, `RUNNING`, `UPDATING`, `STOPPING`, `STOPPED`, `ERROR` or `STATUS_UNKNOWN`.
- `subnet_ids` (**Required**)(Set Of String). The list of VPC subnets identifiers which resource is attached.
- `version` (String). Metastore server version.
- `timeouts` [Block]. 
  - `read` (String). A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) 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.