# ======================== Elasticsearch Configuration =========================# # Please consult the documentation for further information on configuration options: # https://www.elastic.co/guide/en/elasticsearch/reference/index.html # # ---------------------------------- Cluster ----------------------------------- # # Use a descriptive name for your cluster: # cluster.name: zebra-log-cluster # ------------------------------------ Node ------------------------------------ # # Use a descriptive name for the node: # node.name: zebra-log-node-1 # # ----------------------------------- Paths ------------------------------------ # # Path to directory where to store the data (separate multiple locations by comma): # path.data: /global/zebra/elkstack/data/elasticsearch path.repo: /global/zebra/elkstack/backup/elasticsearch # # Path to log files: # path.logs: /global/zebra/elkstack/log/elasticsearch # # ----------------------------------- Memory ----------------------------------- # # Lock the memory on startup: # bootstrap.memory_lock: true # # Make sure that the heap size is set to about half the memory available # on the system and that the owner of the process is allowed to use this # limit. # # Elasticsearch performs poorly when the system is swapping the memory. # # ---------------------------------- Network ----------------------------------- # # Set the bind address to a specific IP (IPv4 or IPv6): network.host: _local_ # # Set a custom port for HTTP: # http.port: 9200 # this disables https on the REST-layer. Not optimal, but logstash and kibana are only communicating with elasticsearch # on the same machine. A bug in the logstash-elasticsearch plugin stops us from deploying to our local testing machines # when using https, because we cannot provide a valid certificate and logstash-elasticsearch always performs a full # certificate validation which fails on the cluster. Once the bug is fixed, we can use https internally. searchguard.ssl.http.enabled: false searchguard.ssl.transport.enabled: true searchguard.ssl.transport.keystore_filepath: server.jks searchguard.ssl.transport.keystore_password: lg1uwKVK0vE4UMWyeIPT searchguard.ssl.transport.keystore_type: JKS searchguard.ssl.transport.truststore_filepath: truststore.jks searchguard.ssl.transport.truststore_password: lg1uwKVK0vE4UMWyeIPT searchguard.ssl.transport.truststore_type: JKS searchguard.ssl.transport.resolve_hostname: false searchguard.ssl.transport.enforce_hostname_verification: false searchguard.enable_snapshot_restore_privilege: true searchguard.authcz.admin_dn: - "E=zebra@bmw.de,CN=lizebrav1.bmwgroup.net,OU=PKI Services,O=Bayerische Motoren Werke AG,L=Munich,ST=Bavaria,C=DE" searchguard.nodes_dn: - "E=zebra@bmw.de,CN=lizebrav1.bmwgroup.net,OU=PKI Services,O=Bayerische Motoren Werke AG,L=Munich,ST=Bavaria,C=DE"