Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • 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 StoreDoc
  • Getting started
    • Resource relationships
    • Networking in Yandex StoreDoc
    • Quotas and limits
    • Storage in Yandex StoreDoc
    • Backups
    • Replication
    • High availability clusters
    • Sharding
    • Host types
    • Users and roles
    • Maintenance
    • Supported clients
    • Yandex StoreDoc settings
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  1. Concepts
  2. Resource relationships

Resource relationships in Yandex StoreDoc

Written by
Yandex Cloud
Updated at May 7, 2026

The main entity Yandex StoreDoc operates is a database cluster.

Each cluster consists of one or multiple database hosts, which are virtual machines with deployed DBMS servers. Cluster hosts may reside in different availability zones and even different availability regions. You can learn more about the Yandex Cloud availability zones in Platform overview.

In a cluster with two or more active hosts, one is automatically selected as the primary replica (master) to process write requests. If the master host fails, Yandex StoreDoc selects a new master from among the available hosts.

A cluster with two or more hosts located in different availability zones is tolerant of a single zone failure.

When creating a cluster, specify:

  • Host class: VM template for deploying cluster hosts. For a list of available host classes and their specs, see Host classes.

  • Environment: Environment where the cluster will be deployed:

    • PRODUCTION: For stable versions of your applications.
    • PRESTABLE: For testing purposes. The prestable environment is similar to the production environment and likewise covered by an SLA, but it is the first to get new features, improvements, and bug fixes. In the prestable environment, you can test new versions for compatibility with your application.

You can access a cluster created in a folder from any VM in the same cloud network. For more information about networking, see this Virtual Private Cloud guide.

Alert

The service can automatically access the system and diagnostic information of your databases to render monitoring charts and maintain your cluster health. It never accesses or uses the data you entered into the database manually.

Be mindful of what is managed by the service and what, by the Yandex Cloud customer. Understanding these areas of management helps you use your cloud resources efficiently and avoid potential database-related issues. For more information, see Zones of control between managed database (MDB) service users and Yandex Cloud.

Was the article helpful?

Previous
Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
Next
Active host classes
© 2026 Direct Cursus Technology L.L.C.