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 Studio
    • 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.
Service page
Yandex Managed Service for OpenSearch
Documentation
Yandex Managed Service for OpenSearch
  • Getting started
    • Resource relationships
    • Host roles
    • Indexes
    • Index policies
    • Searching with OpenSearch
    • Host classes
    • Networking in Managed Service for OpenSearch
    • Quotas and limits
    • Disk types
    • Backups
    • Sharding and replication
    • OpenSearch plugins
    • OpenSearch versioning policy
    • Maintenance
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

  • Selecting storage type when creating a cluster
  • Disk encryption
  1. Concepts
  2. Disk types

Disk types in Managed Service for OpenSearch

Written by
Yandex Cloud
Updated at August 14, 2025
  • Selecting storage type when creating a cluster
  • Disk encryption

Managed Service for OpenSearch allows you to use network and local storage drives for database clusters. Network drives are based on network blocks, which are virtual disks in the Yandex Cloud infrastructure. Local disks are physically located on the cluster servers.

When creating a cluster, you can select the following disk types for data storage:

  • Network HDDs (network-hdd): Most cost-effective option for clusters that do not require high read/write performance.

  • Network SSDs (network-ssd): Balanced solution. Such disks are slower than local SSD storage, but, unlike local disks, they ensure data integrity if Yandex Cloud hardware fails.

  • Non-replicated SSDs (network-ssd-nonreplicated): Network disks with enhanced performance achieved by eliminating redundancy.

    The storage size can only be increased in 93 GB increments.

  • Ultra high-speed network SSDs with three replicas (network-ssd-io-m3): Network disks with the same performance characteristics as non-replicated ones. This disk type provides redundancy.

    Such disks can be increased in size only in 93 GB increments.

  • Local SSDs (local-ssd): Disks with the best performance.

    The size of such a storage can be increased:

    • For Intel Cascade Lake: Only in 100 GB increments.
    • For Intel Ice Lake: In 368 GB increments only.

    For clusters with hosts residing in the ru-central1-d availability zone, local SSD storage is not available if using Intel Cascade Lake.

Note

Up to 5% of disk space is reserved for system use, so the disks may have less available space than indicated when creating a cluster.

For more information about sizes and performance of different disk types, see the Yandex Compute Cloud documentation.

Selecting storage type when creating a clusterSelecting storage type when creating a cluster

The number of hosts with the DATA role you can create together with an OpenSearch cluster depends on the selected storage type:

  • You can create a cluster only with three or more hosts when using the following disk types:

    • Local SSDs (local-ssd)
    • Non-replicated SSDs (network-ssd-nonreplicated)

    This cluster will be fault-tolerant.

    Local SSD storage has an effect on how much a cluster will cost: you pay for it even if it is stopped. For more information, refer to the pricing policy.

  • You can add any number of hosts within the current quota when using the following disk types:

    • Network HDDs (network-hdd)
    • Network SSDs (network-ssd)
    • Ultra high-speed network SSDs with three replicas (network-ssd-io-m3)

For more information about limits on the number of hosts per cluster, see Quotas and limits.

To improve fault tolerance, you can set up index replication (for multi-host cluster configurations only).

Disk encryptionDisk encryption

Note

This feature is in the Preview stage. To get access, contact tech support or your account manager.

When creating or restoring a cluster from a backup, you can encrypt the storage disk with a custom KMS key. To encrypt a disk of an already created cluster, disable encryption, or encrypt a disk with a different key, create a backup of the cluster and restore it with the new settings.

Warning

Encryption is not available for local disks (local-hdd and local-ssd).

To create an encrypted disk, you need the kms.keys.user role or higher.

If you deactivate the key used to encrypt a disk, access to the data will be suspended until you reactivate the key.

Alert

If you delete the key used to encrypt a disk or its version, you will irrevocably lose access to your data. For more information, see this Key Management Service article.

Was the article helpful?

Previous
Quotas and limits
Next
Backups
© 2025 Direct Cursus Technology L.L.C.