[Yandex Cloud documentation](../../index.md) > [Yandex Resource Manager](../index.md) > Concepts > Service resource labels

# Service resource labels


Most Yandex Cloud services support resource labeling.

A _label_ is a key-value pair in `<label_name>=<label_value>` format. You can use labels to break resources into logical groups.

Label operation limits:

* Maximum number of labels per resource: 64.
* Label key parameters:

  * It must be from 1 to 63 characters long.
  * It may contain lowercase Latin letters, numbers, hyphens, and underscores.
  * Use a letter for the first character.

* Label value parameters:

  * It may be up to 63 characters long.
  * It may contain lowercase Latin letters, numbers, hyphens, and underscores.

## Label usage examples {#examples}

* [Viewing service usage details by labels](../../billing/operations/check-charges.md#labels_1).

    For example, you can [view the DataSphere spending details](../../datasphere/operations/community/billing-details.md).

* Searching for resources belonging to the same project, owner, environment, etc.

    For example, you can use the `project:app` label to find the Yandex Cloud resources used in the `app` project.

* Grouping resources by various criteria, such as project, team, environment, application, etc.

    For example, you can use the `environment:production` and `environment:test` labels to mark Yandex Cloud resources as belonging to the production and test environments.

* Automating actions with a resource group, such as launching, stopping, or deleting the labeled resources.

    For example, you can [manage a resource group using Yandex Cloud Functions](../../tutorials/infrastructure-management/serverless-trigger-budget-vm.md).

## Services that support labels {#services}

{% note info %}

Some service resources do not support labels, and some interfaces may not display them. For example, resource labels may not be visible in the management console interface, Cloud Center interface, or Yandex Cloud Billing interface.

{% endnote %}

### Infrastructure and network {#infra}

* [Yandex API Gateway](../../api-gateway/index.md)
* [Yandex Application Load Balancer](../../application-load-balancer/index.md)
* [Yandex Cloud CDN](../../cdn/index.md)
* [Yandex Cloud DNS](../../dns/index.md)
* [Yandex Cloud Logging](../../logging/index.md)
* [Yandex Compute Cloud](../../compute/index.md)
* [Yandex Network Load Balancer](../../network-load-balancer/index.md)
* [Yandex Object Storage](../../storage/index.md)
* [Yandex Virtual Private Cloud](../../vpc/index.md)

### Data platform {#data-platform}

* [Yandex Data Processing](../../data-proc/index.md)
* [Yandex Data Transfer](../../data-transfer/index.md)
* [Yandex DataSphere](../../datasphere/index.md)
* [Yandex Message Queue](../../message-queue/index.md)
* [Yandex Managed Service for Apache Airflow™](../../managed-airflow/index.md)
* [Yandex Managed Service for Apache Kafka®](../../managed-kafka/index.md)
* [Yandex Managed Service for ClickHouse®](../../managed-clickhouse/index.md)
* [Yandex MPP Analytics for PostgreSQL](../../managed-greenplum/index.md)
* [Yandex StoreDoc](../../storedoc/index.md)
* [Yandex Managed Service for MySQL®](../../managed-mysql/index.md)
* [Yandex Managed Service for OpenSearch](../../managed-opensearch/index.md)
* [Yandex Managed Service for PostgreSQL](../../managed-postgresql/index.md)
* [Yandex Managed Service for Valkey™](../../managed-valkey/index.md)
* [Yandex Managed Service for YDB](../../ydb/index.md)
* [Yandex MetaData Hub](../../metadata-hub/index.md) (Yandex Connection Manager and Apache Hive™ Metastore clusters)

### Containers {#containers}

* [Yandex Container Registry](../../container-registry/index.md)
* [Yandex Managed Service for Kubernetes](../../managed-kubernetes/index.md)
* [Yandex Serverless Containers](../../serverless-containers/index.md)

### Serverless computing {#serverless}

* [Yandex Cloud Functions](../../functions/index.md)
* [Yandex IoT Core](../../iot-core/index.md)
* [Yandex Serverless Containers](../../serverless-containers/index.md)
* [Yandex Serverless Integrations](../../serverless-integrations/index.md) (EventRouter)

### Security {#security}

* [Yandex Audit Trails](../../audit-trails/index.md)
* [Yandex Certificate Manager](../../certificate-manager/index.md)
* [Yandex Identity and Access Management](../../iam/index.md)
* [Yandex Key Management Service](../../kms/index.md)
* [Yandex Lockbox](../../lockbox/index.md)

### Developer tools {#developer-tools}

* [Yandex Managed Service for GitLab](../../managed-gitlab/index.md)

### Monitoring and resource management {#resources-operations}

* [Yandex Identity Hub](../../organization/index.md)
* [Yandex Resource Manager](../index.md)

## Use cases {#examples}

* [Creating a budget trigger that invokes a Cloud Functions function to stop VM instances](../../tutorials/infrastructure-management/serverless-trigger-budget-vm.md)

#### Useful links {#see-also}

* [Managing labels](../operations/manage-labels.md)
* [Managing labels in Yandex DataSphere communities](../../datasphere/operations/community/manage-community-labels.md)
* [Managing labels in Yandex DataSphere projects](../../datasphere/operations/projects/manage-project-labels.md)

_Greenplum® and Greenplum Database® are registered trademarks or trademarks of Broadcom Inc. in the United States and/or other countries._

_Apache® and [Apache Hive™](https://hive.apache.org/) are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries._

_ClickHouse® is a registered trademark of [ClickHouse, Inc](https://clickhouse.com)._