Support Matrix

Product and Operating System

We currently only support and test x86_64 architectures.
Encryption at rest for Elasticsearch via dm-crypt is supported on all Linux OSs
Support for the listed Linux distributions requires a native Linux install, e.g., Windows Subsystem for Linux (WSL) is unsupported
*We might ask you to move to newer versions of Amazon Linux as part of our support process

We currently only support and test x86_64 architectures.
*We might ask you to move to newer versions of Amazon Linux as part of our support process
**Zip/tar.gz archives only. RPM installation is not supported on SLES 11.

Auditbeat

Filebeat

Functionbeat

Heartbeat

Metricbeat

Packetbeat

Winlogbeat

* We might ask you to move to newer versions of Amazon Linux as part of our support process.
** Compatibility applies to the bundled CLI for deploying Functionbeat onto serverless frameworks.
Additionally, we provide Beats binaries but not support for Windows XP, Windows Server 2008, OpenSUSE Leap 42, OpenSUSE 13.2, and Oracle Enterprise Linux 6/7 with RHEL Kernel only.
You may also self compile without support on Linux ARM, Linux PPC/PPC64LE, Solaris/SmartOS, and FreeBSD.

Elastic Cloud Enterprise

Supported Docker and Linux Kernel versions:
ECE 1.X requires Docker version 1.11. We highly recommend upgrading your installation to ECE 2.x and using a newer Docker version as specified below.
ECE 2.x supports the following Docker and OS combinations:
- Ubuntu 16.04 with Docker 18.09
- RHEL 7.x with RedHat Docker 1.13
- CentOS 7.x with RedHat Docker 18.09
- SLES 12 with Docker 18.09
ECE requires Linux kernel version 3.10 or higher.
ECE requires kernel memory accounting to be disabled for all memory cgroups. Disable it by passing `cgroup.memory=nokmem` to the kernel at boot time.
**Zip/tar.gz archives only. RPM installation is not supported on SLES 11.

APM Server

* We might ask you to move to newer versions of Amazon Linux as part of our support process.

App Search

* We might ask you to move to newer versions of Amazon Linux as part of our support process.

Elasticsearch and JVM

* Java 9, Java 10, and Java 12 are short term releases. We advise against using them unless you're prepared to handle the fast release cadence this imposes. See Oracle's schedule for JVM support at http://www.oracle.com/technetwork/java/eol-135779.html
** Elastic supports OpenJDK builds by the IcedTea Project as well as those produced by OS vendors in the "Product and Operating System" matrix which have passed the TCK tests and Azul Zulu starting with Elasticsearch 6.6.0 and above.
The Elasticsearch/JVM support information on this page applies to both server and client (e.g., client api) implementations.

Logstash and JVM

Supported Browsers *

* Kibana only
Latest GA versions of listed browsers supported.

Product Compatibility

Compatibility with Elasticsearch (5.x, 6.x)

^ Elasticsearch output compatibility - Beats & Logstash indexing data to Elasticsearch
* We recommend running the latest version of Beats, Logstash, and ES-Hadoop; earlier versions will work with reduced functionality.
** Starting in version 6.3, X-Pack features are included in the default distributions of Elastic Stack. See https://www.elastic.co/products/x-pack/open
*** APM Server 6.7 works with Elasticsearch 7.0, but data must be migrated using the Upgrade Assistant to be visible in Kibana 7.0

Compatibility with Elasticsearch (2.x)

** Beats to Logstash has a separate compatibility chart

Compatibility with Logstash

* Compatibility applies to the monitoring & management Elasticsearch cluster and any Elasticsearch clusters that metrics are routed through. This includes any cluster(s) referenced in the xpack.monitoring.elasticsearch.url and xpack.management.elasticsearch.url settings. It's highly recommended to run the same minor versions across Elasticsearch, Kibana, and Logstash for best monitoring & management functionality. For versions 6.2 and older, X-Pack must be installed on all products.
** Functionbeat is only compatible with Elasticsearch as an output destination. Logstash and other outputs are not supported.

Compatibility with Beats

* Compatibility applies to the monitoring Elasticsearch cluster and any Elasticsearch clusters that metrics are routed through. This includes any cluster(s) referenced in the xpack.monitoring.elasticsearch settings. It's highly recommended to run the same minor versions across Elasticsearch, Kibana, and Beats for best monitoring functionality. For version 6.2, X-Pack must be installed on all products.
** Functionbeat is only compatible with Elasticsearch as an output destination. Logstash and other outputs are not supported.

Compatibility with Elastic Cloud Enterprise

Supported Logstash Plugins

The plugins listed below are maintained and supported by Elastic. Plugin versions that are installable on an Elastic supported Logstash release are considered supported.

The full list of all plugins in the Logstash ecosystem can be found in the product documentation:

• Input plugins
• Codec plugins
• Filter plugins
• Output plugins

Tier 1 Plugins

Definition: These incorporate Logstash plugins that Elastic have published directly and plugins that Elastic has a high degree of experience with. Elastic will provide support to new Support Requests at point of entry for all Severity Levels (1 through 3) but retain the right to downgrade Support Requests to Severity 3 should the root cause be isolated to an external system, service, or library.

* * The S3 input and output plugins only support AWS S3. Other S3 compatible storage solutions are not supported.

** The Ruby filter plugin in supported. The Ruby code executed in the plugin is not supported.

Tier 2 Plugins

Definition: These incorporate Logstash plugins where Elastic has a more limited focus, such that Elastic's ability to effect a solution could be impaired. Elastic will provide support under Severity 3 only.

*** The JMS input plugin is only supported for Solace, ActiveMQ, and ActiveMQ Artemis. All other JMS technologies are not supported.