Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud API concepts
  • Basic principles
    • Resource identification
    • Standard fields
  1. Resources
  2. Standard fields

Standard fields

Written by
Yandex Cloud
Updated at April 23, 2025
View in Markdown

This section lists standard fields that can be found in Yandex Cloud resource views. These fields are unified for all services.

Field name Description
cloud_id* string
ID of the cloud where the folder is located. The field is included in the folder resource view.

The cloud_id and folder_id fields are mutually exclusive.
folder_id* string
ID of the folder where the resource is located. This field is only available in the views of cloud resources, such as disks and VMs.

The cloud_id and folder_id fields are mutually exclusive.
id* string
Resource ID. Generated on the service side. Maximum ID length: 50 characters.
created_at* google.protobuf.Timestamp
Resource creation time in RFC3339 (Timestamps) format.
name string
Resource name. Specified by the user. Maximum name length: 64 characters.
description string
Resource description. Specified by the user. Maximum description length: 256 characters.
zone_id string
ID of the availability zone the resource belongs to.
This field is omitted if the resource does not belong to any zone.
status enum
Resource state. For example: READY, CREATING.
This field is used for resources that take a long time to update. For example, VMs or disks.
labels map<string, string>
Resource labels in key:value format. Specified by the user. Metadata or other arbitrary data can be used as resource labels.

* Required field which is always included in any resource view.

Was the article helpful?

Previous
Resource identification
Next
Overview
© 2026 Direct Cursus Technology L.L.C.