In the management console, navigate to the folder page and select Managed Service for Elasticsearch.
Select a cluster and click Edit in the top panel.
Select the service account you need from the list or create a new one. For more information about setting up a service account, see Configuring access to Object Storage from a cluster.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

To change the settings of the service account used to work with the cluster:

View the description of the CLI command to update the cluster:
```
yc managed-elasticsearch cluster update --help
```
Specify the service account ID in the update cluster command:
```
yc managed-elasticsearch cluster update <cluster_name_or_ID> \
  --service-account-id <service_account_ID>
```
You can request the cluster name and ID with the list of clusters in the folder.

Managed Service for Elasticsearch will run the service account update for the cluster.

Open the current Terraform configuration file that defines your infrastructure.

For more information about creating this file, see Creating clusters.

In the service_account_id field, enter the service account ID:

resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" {
  ...
  service_account_id = <service_account_ID>
}

Make sure the settings are correct.
1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.
2. Run this command:
```
terraform validate
```
  Terraform will show any errors found in your configuration files.
Confirm updating the resources.
1. Run this command to view the planned changes:
```
terraform plan
```
  If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.
2. If everything looks correct, apply the changes:
  1. Run this command:
```
terraform apply
```
  2. Confirm updating the resources.
  3. Wait for the operation to complete.
Time limits
A Terraform provider sets the timeout for Managed Service for Elasticsearch cluster operations:
- Creating a cluster, including by restoring one from a backup: 30 minutes.
- Editing a cluster: 60 minutes.
- Deleting a cluster: 15 minutes.
Operations exceeding the set timeout are interrupted.
How do I change these limits?
Add the timeouts block to the cluster description, for example:

resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" { ... timeouts { create = "1h30m" # 1 hour 30 minutes update = "2h" # 2 hours delete = "30m" # 30 minutes } }

To change service account settings, use the update REST API method for the Cluster resource or the ClusterService/Update gRPC API call and provide the following in the request:

Cluster ID in the clusterId parameter.

You can get the cluster ID with a list of clusters in the folder.
ID of the service account used for cluster operations in the serviceAccountId parameter.

Warning

The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the updateMask parameter as a single comma-separated string.

Warning

If the cluster already uses a service account to access objects from Object Storage, then changing it to a different service account may make these objects unavailable and interrupt the cluster operation. Before changing the service account settings, make sure that the cluster doesn't use the objects in question.

Changing the host class

Management console

CLI

Terraform

API

In the management console, navigate to the folder page and select Managed Service for Elasticsearch.
Select a cluster and click Edit in the top panel.
To change the class of Elasticsearch hosts with the Data node role:
1. Go to the Data node tab.
2. Under Host class , select the class for the host.
To change the class of Elasticsearch hosts with the Master node role:
1. Go to the Master node tab.
2. Under Host class , select the class for the host.
Click Save.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

To change the host class for the cluster:

View the description of the CLI command to update the cluster:
```
yc managed-elasticsearch cluster update --help
```

Specify the host class you need with the Data node and Master node roles in the update cluster command:

yc managed-elasticsearch cluster update <cluster_name_or_ID> \
  --datanode-resource-preset <class_of_hosts_with_the_Data_node_role> \
  --masternode-resource-preset <class_of_hosts_with_the_Master_node_role>

You can request the cluster name and ID with the list of clusters in the folder.

Open the current Terraform configuration file that defines your infrastructure.

For more information about creating this file, see Creating clusters.

For a complete list of available Managed Service for Elasticsearch cluster configuration fields, see the Terraform provider documentation.

In the Managed Service for Elasticsearch cluster description, change the resource_preset_id attribute value under config.data_node.resources or config.master_node.resources:

resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" {
  ...
  config {
    data_node {
      resources {
        resource_preset_id = "<host_class>"
        ...
      }
    }

    master_node {
      resources {
        resource_preset_id = "<host_class>"
        ...
      }
    }
  }
}

Make sure the settings are correct.
1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.
2. Run this command:
```
terraform validate
```
  Terraform will show any errors found in your configuration files.
Confirm updating the resources.
1. Run this command to view the planned changes:
```
terraform plan
```
  If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.
2. If everything looks correct, apply the changes:
  1. Run this command:
```
terraform apply
```
  2. Confirm updating the resources.
  3. Wait for the operation to complete.
Time limits
A Terraform provider sets the timeout for Managed Service for Elasticsearch cluster operations:
- Creating a cluster, including by restoring one from a backup: 30 minutes.
- Editing a cluster: 60 minutes.
- Deleting a cluster: 15 minutes.
Operations exceeding the set timeout are interrupted.
How do I change these limits?
Add the timeouts block to the cluster description, for example:

resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" { ... timeouts { create = "1h30m" # 1 hour 30 minutes update = "2h" # 2 hours delete = "30m" # 30 minutes } }

To change the host class, use the update REST API method for the Cluster resource or the ClusterService/Update gRPC API call and provide the following in the request:

Cluster ID in the clusterId parameter.

You can get the cluster ID with a list of clusters in the folder.
Host class in the following parameters:
- configSpec.elasticsearchSpec.dataNode.resources.resourcePresetId: For hosts with the Data node role.
- configSpec.elasticsearchSpec.masterNode.resources.resourcePresetId: For hosts with the Master node role.
To request a list of supported values, use the list method for the ResourcePreset resources.
List of settings to update in the updateMask parameter.

Warning

Increasing storage size

Make sure the cloud has enough quota to increase the storage size. Open the cloud's Quotas page and check the HDD storage capacity and SSD storage capacity lines under Managed Databases to make sure there is available quota for storage space.

Management console

CLI

Terraform

API

To increase the cluster storage size:

In the management console, navigate to the folder page and select Managed Service for Elasticsearch.
Select a cluster and click Edit in the top panel.
To increase the disk size for Elasticsearch hosts with the Data node role:
1. Go to the Data node tab.
2. Under Storage, specify the disk size.
To increase the disk size for Elasticsearch hosts with the Master node role:
1. Go to the Master node tab.
2. Under Storage, specify the disk size.
Click Save.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

To increase the cluster storage size:

View a description of the CLI update configuration command:
```
yc managed-elasticsearch cluster update --help
```
Specify new storage settings for hosts with the Data node and Master node roles in the update cluster command:
```
yc managed-elasticsearch cluster update <cluster_name_or_ID> \
  --datanode-disk-size <Data_node_storage_size_in_GB> \
  --masternode-disk-size <Master_node_storage_size_in_GB>
```
Where:
- --datanode-disk-size: Storage size in GB for hosts with the Data node role.
- --masternode-disk-size: Storage size in GB for hosts with the Master node role.

You can request the cluster name and ID with the list of clusters in the folder.

To increase the cluster storage size:

Open the current Terraform configuration file that defines your infrastructure.

For more information about creating this file, see Creating clusters.

For a complete list of available Managed Service for Elasticsearch cluster configuration fields, see the Terraform provider documentation.

In the Managed Service for Elasticsearch cluster description, change the disk_size attribute value under config.data_node.resources or config.master_node.resources:

resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" {
  ...
  config {
    data_node {
      resources {
        disk_size = <storage_size_in_GB>
        ...
      }
    }

    master_node {
      resources {
        disk_size = <storage_size_in_GB>
        ...
      }
    }
  }
}

Make sure the settings are correct.
1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.
2. Run this command:
```
terraform validate
```
  Terraform will show any errors found in your configuration files.
Confirm updating the resources.
1. Run this command to view the planned changes:
```
terraform plan
```
  If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.
2. If everything looks correct, apply the changes:
  1. Run this command:
```
terraform apply
```
  2. Confirm updating the resources.
  3. Wait for the operation to complete.
Time limits
A Terraform provider sets the timeout for Managed Service for Elasticsearch cluster operations:
- Creating a cluster, including by restoring one from a backup: 30 minutes.
- Editing a cluster: 60 minutes.
- Deleting a cluster: 15 minutes.
Operations exceeding the set timeout are interrupted.
How do I change these limits?
Add the timeouts block to the cluster description, for example:

resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" { ... timeouts { create = "1h30m" # 1 hour 30 minutes update = "2h" # 2 hours delete = "30m" # 30 minutes } }

To increase the cluster storage size, use the update REST API method for the Cluster resource or the ClusterService/Update gRPC API call and provide the following in the request:

Cluster ID in the clusterId parameter.

You can get the cluster ID with a list of clusters in the folder.
Required storage size (in bytes) in the following parameters:
- configSpec.elasticsearchSpec.dataNode.resources.diskSize: For hosts with the Data node role.
- configSpec.elasticsearchSpec.masterNode.resources.diskSize: For hosts with the Master node role.
List of settings to update in the updateMask parameter.

Warning

Changing Elasticsearch settings

You can change the DBMS settings of the hosts in your cluster.

Warning

You cannot update Elasticsearch settings with the Elasticsearch API.

Management console

CLI

API

Navigate to the folder dashboard and select Managed Service for Elasticsearch.
Select a cluster and click Edit in the top panel.
Change the Elasticsearch settings by clicking Settings under DBMS settings.
Click Save.
Click Save.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

To change Elasticsearch server settings:

View the full list of settings specified for the cluster:

yc managed-elasticsearch cluster get <cluster_name_or_ID> --full

View the description of the CLI command to update the cluster configuration:
```
yc managed-elasticsearch cluster update-config --help
```

Set the required parameter values:

yc managed-elasticsearch cluster update-config <cluster_name_or_ID> \
   --set <parameter_1_name>=<value_1>,<parameter_2_name>=<value_2>,...

All the supported parameters are listed in Elasticsearch settings.

To change Elasticsearch settings, use the update REST API method for the Cluster resource or the ClusterService/Update gRPC API call and provide the following in the request:

Cluster ID in the clusterId parameter.

You can get the cluster ID with a list of clusters in the folder.
Required DBMS values in the configSpec.elasticsearchSpec.dataNode.elastcsearchConfig_7 parameter.
List of settings to update in the updateMask parameter. If you skip this parameter, the API method will reset any cluster settings that are not explicitly specified in the request to their default values.

All supported settings are described in the Elasticsearch settings section and the API reference.

Changing the admin password

Management console

CLI

Terraform

API

In the management console, navigate to the folder page and select Managed Service for Elasticsearch.
Select a cluster and click Edit in the top panel.
Specify the admin user password in the User section.
Click Save.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

To change the admin user's cluster password:

View the description of the CLI command to update the cluster:
```
yc managed-elasticsearch cluster update --help
```
Specify a new password in the cluster update command using one of the available methods:
- Entering a password in interactive mode.
```
yc managed-elasticsearch cluster update <cluster_name> \
  --read-admin-password
```
- Entering a password as plain text (less secure method).
```
yc managed-elasticsearch cluster update <cluster_name> \
  --admin-password <new_password>
```
- Generating a password automatically. The generated password will be output to the console.
```
yc managed-elasticsearch cluster update <cluster_name> \
  --generate-admin-password
```

Managed Service for Elasticsearch will run the admin password update command for the cluster.

Open the current Terraform configuration file that defines your infrastructure.

For more information about creating this file, see Creating clusters.

For a complete list of available Managed Service for Elasticsearch cluster configuration fields, see the Terraform provider documentation.

In the Managed Service for Elasticsearch cluster description, change the admin_password attribute value under config:

resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" {
  ...
  config {
    admin_password = "<new_admin_user_password>"
    ...
  }
}

Make sure the settings are correct.
1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.
2. Run this command:
```
terraform validate
```
  Terraform will show any errors found in your configuration files.
Confirm updating the resources.
1. Run this command to view the planned changes:
```
terraform plan
```
  If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.
2. If everything looks correct, apply the changes:
  1. Run this command:
```
terraform apply
```
  2. Confirm updating the resources.
  3. Wait for the operation to complete.
Time limits
A Terraform provider sets the timeout for Managed Service for Elasticsearch cluster operations:
- Creating a cluster, including by restoring one from a backup: 30 minutes.
- Editing a cluster: 60 minutes.
- Deleting a cluster: 15 minutes.
Operations exceeding the set timeout are interrupted.
How do I change these limits?
Add the timeouts block to the cluster description, for example:

resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" { ... timeouts { create = "1h30m" # 1 hour 30 minutes update = "2h" # 2 hours delete = "30m" # 30 minutes } }

To update the admin user's password, use the update REST API method for the Cluster resource or the ClusterService/Update gRPC API call and provide the following in the request:

Cluster ID in the clusterId parameter.

You can get the cluster ID with a list of clusters in the folder.
New password in the configSpec.adminPassword parameter. The maximum password length is 128 characters.
List of settings to update (in this case, configSpec.adminPassword) in the updateMask parameter.

Warning

Changing additional cluster settings

Management console

CLI

Terraform

API

In the management console, navigate to the folder page and select Managed Service for Elasticsearch.
Select a cluster and click Edit in the top panel.
Change additional cluster settings:
- Maintenance window: Maintenance window settings:
  - To enable maintenance at any time, select arbitrary (default).
  - To specify the preferred maintenance start time, select by schedule and specify the desired day of the week and UTC hour. For example, you can choose a time when the cluster is least loaded.
  Maintenance operations are carried out both on enabled and disabled clusters. They may include updating the DBMS, applying patches, and so on.
- Deletion protection: Manages cluster protection against accidental deletion.
  
  Even with deletion protection enabled, one can still connect to the cluster manually and delete the data.
Set the DBMS settings:

You can configure the Fielddata cache size parameter: a percentage or an absolute value of the dynamic memory structure allocated for the fielddata cache. For example, 10% or 512 MB.
Click Save.

If you do not have the Yandex Cloud (CLI) command line interface yet, install and initialize it.

View the description of the CLI command to update the cluster:
```
yc managed-elasticsearch cluster update --help
```

Run the following command with the list of settings to update:

yc managed-elasticsearch cluster update <cluster_name_or_ID> \
   --plugins <plugin_1_name>,...,<plugin_N_name> \
   --maintenance-window type=<maintenance_type>,`
                       `day=<day_of_week>,`
                       `hour=<hour> \
   --deletion-protection=<deletion_protection>

You can change the following settings:

--plugins: List of Elasticsearch plugins available in the cluster. Plugins that are not on the list will be disabled.
--maintenance-window: Maintenance window settings (including for disabled clusters), where type is the maintenance type:
- anytime (default): Any time.
- weekly: On a schedule. If setting this value, specify the day of week and the hour:
  - day: Day of week in DDD format: MON, TUE, WED, THU, FRI, SAT, or SUN.
  - hour: Hour (UTC) in HH format: 1 to 24.
--deletion-protection: Cluster protection from accidental deletion, true or false.

Even with deletion protection enabled, one can still connect to the cluster manually and delete the data.

You can get the cluster ID and name with the list of clusters in the folder.

Open the current Terraform configuration file that defines your infrastructure.

For more information about creating this file, see Creating clusters.

For a complete list of available Managed Service for Elasticsearch cluster configuration fields, see the Terraform provider documentation.
To set up the maintenance window (for disabled clusters as well), add the maintenance_window block to the cluster description:
```
resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" {
  ...
  maintenance_window {
    type = <maintenance_type>
    day  = <day_of_week>
    hour = <hour>
  }
  ...
}
```
Where:
- type: Maintenance type. The possible values include:
  - anytime: Anytime.
  - weekly: By schedule.
- day: Day of the week for the weekly type in DDD format, e.g., MON.
- hour: Hour of the day for the weekly type in the HH format, e.g., 21.
To change the list of Elasticsearch plugins, change the value of the plugins parameter under config in the cluster description:
```
resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" {
  ...
  config {
    plugins = [ "<list_of_plugin_names>" ]
  }
}
```
Plugins that are not on the list will be disabled.
To enable cluster protection against accidental deletion by a user of your cloud, add the deletion_protection field set to true to your cluster description:
```
resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" {
  ...
  deletion_protection = <deletion_protection>
}
```
Where deletion_protection is the cluster deletion protection, true or false.

Even with cluster deletion protection enabled, one can still delete a user or database or connect manually and delete the database contents.
Make sure the settings are correct.
1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.
2. Run this command:
```
terraform validate
```
  Terraform will show any errors found in your configuration files.
Confirm updating the resources.
1. Run this command to view the planned changes:
```
terraform plan
```
  If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.
2. If everything looks correct, apply the changes:
  1. Run this command:
```
terraform apply
```
  2. Confirm updating the resources.
  3. Wait for the operation to complete.
Time limits
A Terraform provider sets the timeout for Managed Service for Elasticsearch cluster operations:
- Creating a cluster, including by restoring one from a backup: 30 minutes.
- Editing a cluster: 60 minutes.
- Deleting a cluster: 15 minutes.
Operations exceeding the set timeout are interrupted.
How do I change these limits?
Add the timeouts block to the cluster description, for example:

resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" { ... timeouts { create = "1h30m" # 1 hour 30 minutes update = "2h" # 2 hours delete = "30m" # 30 minutes } }

To change additional cluster settings, use the update REST API method for the Cluster resource or the ClusterService/Update gRPC API call and provide the following in the request:

Cluster ID in the clusterId parameter.

You can get the cluster ID with a list of clusters in the folder.
List of Elasticsearch plugins in the plugins parameter.
Maintenance window settings (including for disabled clusters) in the maintenanceWindow parameter.
Cluster deletion protection settings in the deletionProtection parameter.

Even with deletion protection enabled, one can still connect to the cluster manually and delete the data.
Settings for access from Yandex Data Transfer in the configSpec.access.dataTransfer parameter.

Warning

Updating Elasticsearch cluster settings

Changing service account settingsChanging service account settings

Changing the host classChanging the host class

Increasing storage sizeIncreasing storage size

Changing Elasticsearch settingsChanging Elasticsearch settings

Changing the admin passwordChanging the admin password

Changing additional cluster settingsChanging additional cluster settings

Was the article helpful?

Changing service account settings

Changing the host class

Increasing storage size

Changing Elasticsearch settings

Changing the admin password

Changing additional cluster settings