Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Managed Service for Elasticsearch
  • Getting started
    • All guides
      • Information about existing clusters
      • Creating a cluster
        • Updating cluster settings
        • Updating the Elasticsearch version and edition
        • Managing plugins
        • Managing extensions
      • Stopping and starting a cluster
      • Managing hosts
      • Migrating hosts to a different availability zone
      • Managing backups
      • Configuring access to Object Storage
      • Deleting a cluster
    • User management
  • Access management
  • Pricing policy
  • CLI reference
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

  • Retrieving a list of installed plugins
  • Editing a list of installed plugins
  • Supported Elasticsearch plugins
  1. Step-by-step guides
  2. Clusters
  3. Updating parameters
  4. Managing plugins

Managing Elasticsearch plugins

Written by
Yandex Cloud
Updated at May 13, 2025
  • Retrieving a list of installed plugins
  • Editing a list of installed plugins
  • Supported Elasticsearch plugins

Warning

Yandex Managed Service for Elasticsearch is unavailable as of April 11, 2024.

You can create an OpenSearch cluster in Yandex Cloud as an alternative to Elasticsearch.

When creating or updating a cluster in Managed Service for Elasticsearch, you can specify a list of necessary plugins and they will be installed in the cluster automatically. A full list of available plugins is given below.

Retrieving a list of installed pluginsRetrieving a list of installed plugins

CLI
API

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 get a list of cluster plugins, run the following command:

yc managed-elasticsearch cluster get <cluster_name_or_ID>

Enabled plugins will be on the plugins list.

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

To get a list of installed plugins, use the get REST API method for the Cluster resource or the ClusterService/Get gRPC API call and provide the cluster ID in the clusterId request parameter.

Enabled plugins will be on the plugins list.

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

Editing a list of installed pluginsEditing a list of installed plugins

CLI
Terraform
API

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 update cluster plugins, provide the plugin list in the --plugins parameter of the CLI command. Plugins that are not on the list will be disabled.

yc managed-elasticsearch cluster update <cluster_name_or_ID> \
   --plugins=<plugin_1_name>,...,<plugin_N_name>

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

  1. Open the current Terraform configuration file with an infrastructure plan.

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

  2. In the Managed Service for Elasticsearch cluster description, add the plugins field with a list of plugins to the config section:

    resource "yandex_mdb_elasticsearch_cluster" "<cluster_name>" {
      ...
      config {
        ...
        plugins = [ "<list_of_plugin_names>" ]
        ...
      }
      ...
    }
    
  3. 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.

  4. 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.

For more information, see the Terraform provider documentation.

To update the list of installed plugins, 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 plugins in the configSpec.elasticsearchSpec.plugins parameter. Plugins that are not on the list will be disabled.

  • List of cluster configuration fields to update in the updateMask 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.

Supported Elasticsearch pluginsSupported Elasticsearch plugins

All supported plugins are listed here:

  • analysis-icu

    Adds the Lucene ICU module with extended Unicode support using the ICU libraries. It enables better analysis of Asian languages, Unicode normalization, Unicode-aware case folding, collation support, and transliteration.

  • analysis-kuromoji

    Adds the Lucene kuromoji analysis module for Japanese.

  • analysis-nori

    Adds the Lucene nori analysis module for Korean.

  • analysis-phonetic

    Provides lexeme filters that convert expressions to their phonetic representation using Soundex, Metaphone, and other algorithms.

  • analysis-smartcn

    Adds the Lucene's Smart Chinese analysis module for Chinese or mixed Chinese-English text.

  • analysis-stempel

    Adds the Lucene's Stempel analysis module for Polish.

  • analysis-ukrainian

    Adds the Lucene's UkrainianMorfologikAnalyzer analysis module providing stemming for Ukrainian.

  • ingest-attachment

    Extracts file attachments in common formats (such as PPT, XLS, and PDF) using the Apache Tika™ text extraction library.

  • mapper-annotated-text

    Indexes text that is a combination of free-text and special markup. Such combinations are typically used to identify items of interest such as people or organizations.

  • mapper-murmur3

    Computes hashes of field values at index-time and stores them in the index.

  • mapper-size

    Provides the _size metadata field, which indexes the size (in bytes) of the original _source field.

  • repository-azure

    Adds support for Azure Blob storage as a repository for snapshots.

  • repository-gcs

    Adds support for Google Cloud Storage as a repository for snapshots.

  • repository-hdfs

    Adds support for the HDFS file system as a repository for snapshots.

  • repository-s3

    Adds support for AWS S3 as a repository for snapshots.

  • store-smb

    Fixes bugs in Windows SMB and Java on Windows.

  • transport-nio

    Server/client non-blocking networking library built with Netty.

For more information, see the Elasticsearch documentation.

Was the article helpful?

Previous
Updating the Elasticsearch version and edition
Next
Managing extensions
Yandex project
© 2025 Yandex.Cloud LLC