Contact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.

Stopping and restarting a Yandex StoreDoc cluster

Written by
Updated at May 5, 2026

If necessary, you can stop and restart your Yandex StoreDoc cluster. During cluster downtime, you only pay for allocated storage and backup space, as per the pricing policy.

Alert

If a cluster uses local SSD storage (local-ssd), its computing resources are not released when it's stopped. This means that you are charged in full even for a stopped cluster.

Stopping a cluster

  1. Open the folder dashboard.
  2. Navigate to the Yandex StoreDoc service.
  3. Locate the cluster you need in the list, click , and select Stop.
  4. Confirm that you want to stop the cluster by clicking Stop.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

To stop a cluster, run this command:

yc managed-mongodb cluster stop <cluster_name_or_ID>

You can get the cluster’s name and ID from the list of clusters in your folder.

  1. Get an IAM token for API authentication and place it in an environment variable:

    export IAM_TOKEN="<IAM_token>"

  2. Call the Cluster.Stop method, e.g., via the following cURL request:

    curl \
    --request POST \
    --header "Authorization: Bearer $IAM_TOKEN" \
    --header "Content-Type: application/json" \
    --url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/clusters/<cluster_ID>:stop'

    You can get the cluster ID from the list of clusters in your folder.

  3. Check the server response to make sure your request was successful.

  1. Get an IAM token for API authentication and place it in an environment variable:

    export IAM_TOKEN="<IAM_token>"

  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi

    Below, we assume that the repository contents reside in the ~/cloudapi/ directory.

  3. Call the ClusterService.Stop method, e.g., via the following gRPCurl request:

    grpcurl \
    -format json \
    -import-path ~/cloudapi/ \
    -import-path ~/cloudapi/third_party/googleapis/ \
    -proto ~/cloudapi/yandex/cloud/mdb/mongodb/v1/cluster_service.proto \
    -rpc-header "Authorization: Bearer $IAM_TOKEN" \
    -d '{
          "cluster_id": "<cluster_ID>"
        }' \
    mdb.api.cloud.yandex.net:443 \
    yandex.cloud.mdb.mongodb.v1.ClusterService.Stop

    You can get the cluster ID from the list of clusters in your folder.

  4. Check the server response to make sure your request was successful.

Starting a cluster

You can restart a cluster if its status is STOPPED.

  1. Open the folder dashboard.
  2. Navigate to the Yandex StoreDoc service.
  3. In the list, locate the stopped cluster you want to restart, click , and select Start.
  4. In the dialog box that opens, click Start to confirm the cluster launch.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

To start a stopped cluster, run this command:

yc managed-mongodb cluster start <cluster_name_or_ID>

You can get the cluster’s name and ID from the list of clusters in your folder.

  1. Get an IAM token for API authentication and place it in an environment variable:

    export IAM_TOKEN="<IAM_token>"

  2. Call the Cluster.Start method, e.g., via the following cURL request:

    curl \
    --request POST \
    --header "Authorization: Bearer $IAM_TOKEN" \
    --header "Content-Type: application/json" \
    --url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/clusters/<cluster_ID>:start'

    You can get the cluster ID from the list of clusters in your folder.

  3. Check the server response to make sure your request was successful.

  1. Get an IAM token for API authentication and place it in an environment variable:

    export IAM_TOKEN="<IAM_token>"

  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi

    Below, we assume that the repository contents reside in the ~/cloudapi/ directory.

  3. Call the ClusterService.Start method, e.g., via the following gRPCurl request:

    grpcurl \
    -format json \
    -import-path ~/cloudapi/ \
    -import-path ~/cloudapi/third_party/googleapis/ \
    -proto ~/cloudapi/yandex/cloud/mdb/mongodb/v1/cluster_service.proto \
    -rpc-header "Authorization: Bearer $IAM_TOKEN" \
    -d '{
          "cluster_id": "<cluster_ID>"
        }' \
    mdb.api.cloud.yandex.net:443 \
    yandex.cloud.mdb.mongodb.v1.ClusterService.Start

    You can get the cluster ID from the list of clusters in your folder.

  4. Check the server response to make sure your request was successful.

Previous
Yandex StoreDoc version update
Next
Managing cluster hosts