Plugins extend the core functionality of Elasticsearch. There are many suitable plugins, including:
- The discovery plugins, such as the cloud AWS plugin that allows discovering nodes on EC2 instances
- The analysis plugins, to provide analyzers targeted at languages other than English
- The scripting plugins, to provide additional scripting languages
Plugins can come from different sources: The official ones created or at least maintained by Elastic, community-sourced plugins from other users, and custom plugins that you provide. Some of the official plugins are always provided with our service and you just have to add them to your cluster.
To learn more about what official and community-sourced plugins are available, see Elasticsearch Plugins and Integrations.
We make it easy to add plugins to your Elasticsearch cluster by providing a variety of compatible plugins that work with your version of Elasticsearch. One advantage of the official plugins is that you generally don’t have to worry about also upgrading plugins when you upgrade to a new Elasticsearch version, unless there are breaking changes. The plugins simply are upgraded along with the rest of your cluster.
You can find the list of the plugins provided with Elastic Cloud on the Elasticsearch Edit page for your deployment in the Elastic Cloud Console.
Different versions of Elasticsearch support different plugins.
There are two ways to add plugins to a cluster in Elastic Cloud:
- Select one of the plugins we make available on the Edit page for your Elasticsearch cluster in the Elastic Cloud Console and click Save changes. The cluster is then updated with new nodes that have the plugin installed.
Upload a custom plugin to your cluster to install it. Custom plugins can include the official Elasticsearch plugins not provided with Elastic Cloud, any of the community-sourced plugins, or plugins that you write yourself.
Uploading custom plugins is available only to Gold and Platinum subscriptions. For more information, see Uploading Custom Plugins, Dictionaries, and Scripts.
There are some restrictions that apply to plugins with Elastic Cloud:
- Kibana plugins are not supported.
- Some Elasticsearch plugins do not apply to the Elastic Cloud. For example, you won’t ever need to change discovery, as Elastic Cloud handles how nodes discover one another.
- In Elasticsearch 1.x, custom plugins are not available. If you need a custom plugin, use a supported Elasticsearch version.
- In Elasticsearch 5.0 and later, site plugins are no longer supported. This change does not affect the site plugins Elastic Cloud might provide out of the box, such as Kopf or Head, since these site plugins are serviced by our proxies and not Elasticsearch itself.
- In Elasticsearch 6.0 and later, site plugins such as Kopf and Paramedic are no longer provided. We recommend that you either use our cluster performance metrics or enable the X-Pack monitoring features if you want more detailed information.