To use X-Pack for Elasticsearch and Kibana, you need:
- Elasticsearch 5.1.1 - Installing Elasticsearch
- Kibana 5.1.1 - Getting Kibana Up and Running

You must run the version of X-Pack that matches the version of Elasticsearch you are running.
To install X-Pack:
Run
bin/elasticsearch-plugin install
fromES_HOME
on each node in your cluster:bin/elasticsearch-plugin install x-pack
If you are using a DEB/RPM distribution of Elasticsearch, run the installation with superuser permissions. To perform an offline installation, download the X-Pack binaries.
Confirm that you want to grant X-Pack additional permissions. X-Pack needs these permissions to set the threat context loader during install so Watcher can send email notifications.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: plugin requires additional permissions @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ * java.lang.RuntimePermission accessClassInPackage.com.sun.activation.registries * java.lang.RuntimePermission getClassLoader * java.lang.RuntimePermission setContextClassLoader * java.lang.RuntimePermission setFactory * java.security.SecurityPermission createPolicy.JavaPolicy * java.security.SecurityPermission getPolicy * java.security.SecurityPermission putProviderProperty.BC * java.security.SecurityPermission setPolicy * java.util.PropertyPermission * read,write * java.util.PropertyPermission sun.nio.ch.bugLevel write * javax.net.ssl.SSLPermission setHostnameVerifier See http://docs.oracle.com/javase/8/docs/technotes/guides/security/permissions.html for descriptions of what these permissions allow and the associated risks. Continue with installation? [y/N]y
Specify the
--batch
option when running the install command to automatically grant these permissions and bypass this install prompt.If you have disabled automatic index creation in Elasticsearch, configure
action.auto_create_index
inelasticsearch.yml
to allow X-Pack to create the following indices:action.auto_create_index: .security,.monitoring*,.watches,.triggered_watches,.watcher-history*
Start Elasticsearch.
bin/elasticsearch
Install X-Pack into Kibana by running
bin/kibana-plugin
in your Kibana installation directory.bin/kibana-plugin install x-pack
Start Kibana.
bin/kibana
To verify X-Pack installation, point your web browser at http://localhost:5601/
to open Kibana. You should be prompted to log in to Kibana. To log in, you can
use the built-in elastic
user and the password changeme
.

SSL/TLS encryption is disabled by default, which means user credentials are passed in the clear. Do not deploy to production without enabling encryption! For more information, see Encrypting Communications.
You must also change the passwords for the built-in elastic
user and the
kibana
user that enables Kibana to communicate with elasticsearch before
deploying to production. See Built-in Users for more information.
Installing X-Pack on a DEB/RPM Package Installation
If you use the DEB/RPM packages to install Elasticsearch, by default Elasticsearch
is installed in /usr/share/elasticsearch
and the configuration files are stored
in /etc/elasticsearch
. (For the complete list of default paths, see
Debian Directory Layout and
RPM Directory Layout in the Elasticsearch Reference.)
To install X-Pack on a DEB/RPM package installation, you need to run
bin/plugin install
from the /usr/share/elasticsearch
directory with superuser
permissions:
cd /usr/share/elasticsearch sudo bin/elasticsearch-plugin install x-pack

If the configuration files are not in /etc/elasticsearch
you
need to specify the location of the configuration files by
setting the system property`es.path.conf` to the config path via
ES_JAVA_OPTS="-Des.path.conf=<path>"
or by setting the
environment variable CONF_DIR
via CONF_DIR=<path>
.
Installing X-Pack on Offline Machines
The bin/elasticsearch-plugin
install script requires direct Internet access
to download and install X-Pack. If your server doesn’t have Internet access, you
can manually download and install X-Pack.
To install X-Pack on a machine that doesn’t have Internet access:
-
Manually download the X-Pack zip file:
https://artifacts.elastic.co/downloads/packs/x-pack/x-pack-5.1.1.zip
(sha1) - Transfer the zip file to a temporary directory on the offline machine. (Do NOT put the file in the Elasticsearch plugins directory.)
Run
bin/elasticsearch-plugin install
from the Elasticsearch install directory and specify the location of the X-Pack zip file. For example:bin/elasticsearch-plugin install file:///path/to/file/x-pack-5.1.1.zip
You must specify an absolute path to the zip file after the
file://
protocol.Run
bin/kibana-plugin install
from the Kibana install directory and specify the location of the X-Pack zip file. (The Elasticsearch and Kibana plugins are included in the same zip file.) For example:bin/kibana-plugin install file:///path/to/file/x-pack-5.1.1.zip
Enabling and Disabling X-Pack Features
By default, all X-Pack features are enabled. You can explicitly enable or
disable X-Pack features in elasticsearch.yml
and kibana.yml
:
Setting | Description |
---|---|
| Set to |
| Set to |
| Set to |
| Set to |
| Set to |
Upgrading X-Pack
To upgrade X-Pack:
- Stop Elasticsearch.
Uninstall X-Pack from Elasticsearch:
bin/elasticsearch-plugin remove x-pack
Install the new version of X-Pack into Elasticsearch.
bin/elasticsearch-plugin install x-pack
Restart Elasticsearch.
If you’re upgrading a production cluster, perform a rolling upgrade to ensure recovery is as quick as possible. Rolling upgrades are supported when upgrading to a new minor version. A full cluster restart is required when upgrading to a new major version.
Uninstall X-Pack from Kibana:
bin/kibana-plugin remove x-pack
Install the new version of X-Pack into Kibana.
bin/kibana-plugin install x-pack
- Restart Kibana.
Uninstalling X-Pack
To uninstall X-Pack:
- Stop Elasticsearch.
Remove X-Pack from Elasticsearch:
bin/elasticsearch-plugin remove x-pack
- Restart Elasticsearch.
Remove X-Pack from Kibana:
bin/kibana-plugin remove x-pack
- Restart Kibana.