[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-9967":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":34,"readmeContent":35,"aiSummary":36,"trendingCount":16,"starSnapshotCount":16,"syncStatus":37,"lastSyncTime":38,"discoverSource":39},9967,"docker-elk","deviantony\u002Fdocker-elk","deviantony","The Elastic stack (ELK) powered by Docker and Compose.","",null,"Shell",18369,6922,327,5,0,1,8,31,7,79.1,"MIT License",false,"main",true,[27,28,29,30,31,32,33],"docker","docker-compose","elasticsearch","elk","kibana","logstash","searchguard","2026-06-12 04:00:47","# Elastic stack (ELK) on Docker\n\n[![Elastic Stack version](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FElastic%20Stack-9.3.4-00bfb3?style=flat&logo=elastic-stack)](https:\u002F\u002Fwww.elastic.co\u002Fblog\u002Fcategory\u002Freleases)\n[![Build Status](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg?branch=main)](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Factions\u002Fworkflows\u002Fci.yml?query=branch%3Amain)\n\nRun the latest version of the [Elastic stack][elk-stack] with Docker and Docker Compose.\n\nIt gives you the ability to analyze any data set by using the searching\u002Faggregation capabilities of Elasticsearch and\nthe visualization power of Kibana.\n\nBased on the [official Docker images][elastic-docker] from Elastic:\n\n* [Elasticsearch](https:\u002F\u002Fgithub.com\u002Felastic\u002Felasticsearch\u002Ftree\u002Fmain\u002Fdistribution\u002Fdocker)\n* [Logstash](https:\u002F\u002Fgithub.com\u002Felastic\u002Flogstash\u002Ftree\u002Fmain\u002Fdocker)\n* [Kibana](https:\u002F\u002Fgithub.com\u002Felastic\u002Fkibana\u002Ftree\u002Fmain\u002Fsrc\u002Fdev\u002Fbuild\u002Ftasks\u002Fos_packages\u002Fdocker_generator)\n\nOther available stack variants:\n\n* [`tls`](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Ftree\u002Ftls): TLS encryption enabled in Elasticsearch, Kibana (opt in),\n  and Fleet\n\n> [!IMPORTANT]\n> [Platinum][subscriptions] features are enabled by default for a [trial][license-mngmt] duration of **30 days**. After\n> this evaluation period, you will retain access to all the free features included in the Open Basic license seamlessly,\n> without manual intervention required, and without losing any data. Refer to the [How to disable paid\n> features](#how-to-disable-paid-features) section to opt out of this behaviour.\n\n---\n\n## tl;dr\n\n```sh\ndocker compose up setup\n```\n\n```sh\ndocker compose up\n```\n\n\u003Cpicture>\n  \u003Csource media=\"(prefers-color-scheme: dark)\" srcset=\"https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002F6f67cbc0-ddee-44bf-8f4d-7fd2d70f5217\">\n  \u003Cimg alt=\"Animated demo\" src=\"https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002F501a340a-e6df-4934-90a2-6152b462c14a\">\n\u003C\u002Fpicture>\n\n---\n\n## Philosophy\n\nThe main goal of docker-elk is to make the Elastic stack as easy as possible to get into. It is **not a blueprint for a\nproduction-ready deployment**, but rather a _template_ that promotes tweaking and exploration.\n\nThe authors believe in good documentation over elaborate automation. The project's default configuration is purposely\nminimal and unopinionated. The initial setup does not rely on any external dependency, and uses as little scripting as\nnecessary to get things up and running.\n\n---\n\n## Contents\n\n1. [Requirements](#requirements)\n   * [Host setup](#host-setup)\n   * [Docker Desktop](#docker-desktop)\n     * [Windows](#windows)\n     * [macOS](#macos)\n1. [Usage](#usage)\n   * [Bringing up the stack](#bringing-up-the-stack)\n   * [Initial setup](#initial-setup)\n     * [Setting up user authentication](#setting-up-user-authentication)\n     * [Injecting data](#injecting-data)\n   * [Cleanup](#cleanup)\n   * [Version selection](#version-selection)\n1. [Configuration](#configuration)\n   * [How to configure Elasticsearch](#how-to-configure-elasticsearch)\n   * [How to configure Kibana](#how-to-configure-kibana)\n   * [How to configure Logstash](#how-to-configure-logstash)\n   * [How to disable paid features](#how-to-disable-paid-features)\n   * [How to scale out the Elasticsearch cluster](#how-to-scale-out-the-elasticsearch-cluster)\n   * [How to re-execute the setup](#how-to-re-execute-the-setup)\n   * [How to reset a password programmatically](#how-to-reset-a-password-programmatically)\n1. [Extensibility](#extensibility)\n   * [How to add plugins](#how-to-add-plugins)\n   * [How to enable the provided extensions](#how-to-enable-the-provided-extensions)\n1. [JVM tuning](#jvm-tuning)\n   * [How to specify the amount of memory used by a service](#how-to-specify-the-amount-of-memory-used-by-a-service)\n   * [How to enable a remote JMX connection to a service](#how-to-enable-a-remote-jmx-connection-to-a-service)\n1. [Going further](#going-further)\n   * [Plugins and integrations](#plugins-and-integrations)\n\n## Requirements\n\n### Host setup\n\n* [Docker Engine][docker-install] version **18.06.0** or newer\n* [Docker Compose][compose-install] version **2.0.0** or newer\n* 1.5 GB of RAM\n\n> [!NOTE]\n> Especially on Linux, make sure your user has the [required permissions][linux-postinstall] to interact with the Docker\n> daemon.\n\nBy default, the stack exposes the following ports:\n\n* 5044: Logstash Beats input\n* 50000: Logstash TCP input\n* 9600: Logstash monitoring API\n* 9200: Elasticsearch HTTP\n* 9300: Elasticsearch TCP transport\n* 5601: Kibana\n\n> [!WARNING]\n> Elasticsearch's [bootstrap checks][bootstrap-checks] were purposely disabled to facilitate the setup of the Elastic\n> stack in development environments. For production setups, we recommend users to set up their host according to the\n> instructions from the Elasticsearch documentation: [Important System Configuration][es-sys-config].\n\n### Docker Desktop\n\n#### Windows\n\nIf you are using the legacy Hyper-V mode of _Docker Desktop for Windows_, ensure that [File\nSharing][desktop-filesharing] is enabled for the `C:` drive.\n\n#### macOS\n\nThe default configuration of _Docker Desktop for Mac_ allows mounting files from `\u002FUsers\u002F`, `\u002FVolume\u002F`, `\u002Fprivate\u002F`,\n`\u002Ftmp` and `\u002Fvar\u002Ffolders` exclusively. Make sure the repository is cloned in one of those locations or follow the\ninstructions from the [documentation][desktop-filesharing] to add more locations.\n\n## Usage\n\n> [!WARNING]\n> You must rebuild the stack images with `docker compose build` whenever you switch branch or update the\n> [version](#version-selection) of an already existing stack.\n\n### Bringing up the stack\n\nClone this repository onto the Docker host that will run the stack with the command below:\n\n```sh\ngit clone https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk.git\n```\n\nThen, initialize the Elasticsearch users and groups required by docker-elk by executing the command:\n\n```sh\ndocker compose up setup\n```\n\nOptionally (but highly recommended), generate encryption keys for Kibana using the following command and copy its output\nto the Kibana configuration file (`kibana\u002Fconfig\u002Fkibana.yml`):\n\n```sh\ndocker compose up kibana-genkeys\n```\n\nIf everything went well and the setup completed without error, start the other stack components:\n\n```sh\ndocker compose up\n```\n\n> [!NOTE]\n> You can also run all services in the background (detached mode) by appending the `-d` flag to the above command.\n\nGive Kibana about a minute to initialize, then access the Kibana web UI by opening \u003Chttp:\u002F\u002Flocalhost:5601> in a web\nbrowser and use the following (default) credentials to log in:\n\n* user: *elastic*\n* password: *changeme*\n\n> [!NOTE]\n> Upon the initial startup, the `elastic`, `logstash_internal` and `kibana_system` Elasticsearch users are initialized\n> with the values of the passwords defined in the [`.env`](.env) file (_\"changeme\"_ by default). The first one is the\n> [built-in superuser][builtin-users], the other two are used by Kibana and Logstash respectively to communicate with\n> Elasticsearch. This task is only performed during the _initial_ startup of the stack. To change users' passwords\n> _after_ they have been initialized, please refer to the instructions in the next section.\n\n### Initial setup\n\n#### Setting up user authentication\n\n> [!NOTE]\n> Refer to [Security settings in Elasticsearch][es-security] to disable authentication.\n\n> [!WARNING]\n> Starting with Elastic v8.0.0, it is no longer possible to run Kibana using the bootstrapped privileged `elastic` user.\n\nThe _\"changeme\"_ password set by default for all aforementioned users is **unsecure**. For increased security, we will\nreset the passwords of all aforementioned Elasticsearch users to random secrets.\n\n1. Reset passwords for default users\n\n    The commands below reset the passwords of the `elastic`, `logstash_internal` and `kibana_system` users. Take note\n    of them.\n\n    ```sh\n    docker compose exec elasticsearch bin\u002Felasticsearch-reset-password --batch --user elastic\n    ```\n\n    ```sh\n    docker compose exec elasticsearch bin\u002Felasticsearch-reset-password --batch --user logstash_internal\n    ```\n\n    ```sh\n    docker compose exec elasticsearch bin\u002Felasticsearch-reset-password --batch --user kibana_system\n    ```\n\n    If the need for it arises (e.g. if you want to [collect monitoring information][ls-monitoring] through Beats and\n    other components), feel free to repeat this operation at any time for the rest of the [built-in\n    users][builtin-users].\n\n1. Replace usernames and passwords in configuration files\n\n    Replace the password of the `elastic` user inside the `.env` file with the password generated in the previous step.\n    Its value isn't used by any core component, but [extensions](#how-to-enable-the-provided-extensions) use it to\n    connect to Elasticsearch.\n\n    > [!NOTE]\n    > In case you don't plan on using any of the provided [extensions](#how-to-enable-the-provided-extensions), or\n    > prefer to create your own roles and users to authenticate these services, it is safe to remove the\n    > `ELASTIC_PASSWORD` entry from the `.env` file altogether after the stack has been initialized.\n\n    Replace the password of the `logstash_internal` user inside the `.env` file with the password generated in the\n    previous step. Its value is referenced inside the Logstash pipeline file (`logstash\u002Fpipeline\u002Flogstash.conf`).\n\n    Replace the password of the `kibana_system` user inside the `.env` file with the password generated in the previous\n    step. Its value is referenced inside the Kibana configuration file (`kibana\u002Fconfig\u002Fkibana.yml`).\n\n    See the [Configuration](#configuration) section below for more information about these configuration files.\n\n1. Restart Logstash and Kibana to re-connect to Elasticsearch using the new passwords\n\n    ```sh\n    docker compose up -d logstash kibana\n    ```\n\n> [!NOTE]\n> Learn more about the security of the Elastic stack at [Secure the Elastic Stack][sec-cluster].\n\n#### Injecting data\n\nLaunch the Kibana web UI by opening \u003Chttp:\u002F\u002Flocalhost:5601> in a web browser, and use the following credentials to log\nin:\n\n* user: *elastic*\n* password: *\\\u003Cyour generated elastic password>*\n\nNow that the stack is fully configured, you can go ahead and inject some log entries.\n\nThe shipped Logstash configuration allows you to send data over the TCP port 50000. For example, you can use one of the\nfollowing commands — depending on your installed version of `nc` (Netcat) — to ingest the content of the log file\n`\u002Fpath\u002Fto\u002Flogfile.log` in Elasticsearch, via Logstash:\n\n```sh\n# Execute `nc -h` to determine your `nc` version\n\ncat \u002Fpath\u002Fto\u002Flogfile.log | nc -q0 localhost 50000          # BSD\ncat \u002Fpath\u002Fto\u002Flogfile.log | nc -c localhost 50000           # GNU\ncat \u002Fpath\u002Fto\u002Flogfile.log | nc --send-only localhost 50000  # nmap\n```\n\nYou can also load the sample data provided by your Kibana installation.\n\n### Cleanup\n\nElasticsearch data is persisted inside a volume by default.\n\nIn order to entirely shutdown the stack and remove all persisted data, use the following Docker Compose command:\n\n```sh\ndocker compose --profile=setup down -v\n```\n\n### Version selection\n\nThis repository stays aligned with the latest version of the Elastic stack. The `main` branch tracks the current major\nversion (9.x).\n\nTo use a different version of the core Elastic components, simply change the version number inside the [`.env`](.env)\nfile. If you are upgrading an existing stack, remember to rebuild all container images using the `docker compose build`\ncommand.\n\n> [!IMPORTANT]\n> Always pay attention to the [official upgrade instructions][upgrade] for each individual component before performing a\n> stack upgrade.\n\nOlder major versions are also supported on separate branches:\n\n* [`release-8.x`](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Ftree\u002Frelease-8.x): 8.x series\n* [`release-7.x`](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Ftree\u002Frelease-7.x): 7.x series (End-of-Life)\n* [`release-6.x`](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Ftree\u002Frelease-6.x): 6.x series (End-of-life)\n* [`release-5.x`](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Ftree\u002Frelease-5.x): 5.x series (End-of-life)\n\n## Configuration\n\n> [!IMPORTANT]\n> Configuration is not dynamically reloaded, you will need to restart individual components after any configuration\n> change.\n\n### How to configure Elasticsearch\n\nThe Elasticsearch configuration is stored in [`elasticsearch\u002Fconfig\u002Felasticsearch.yml`][config-es].\n\nYou can also specify the options you want to override by setting environment variables inside the Compose file:\n\n```yml\nelasticsearch:\n\n  environment:\n    network.host: _non_loopback_\n    cluster.name: my-cluster\n```\n\nPlease refer to the following documentation page for more details about how to configure Elasticsearch inside Docker\ncontainers: [Install Elasticsearch with Docker][es-docker].\n\n### How to configure Kibana\n\nThe Kibana default configuration is stored in [`kibana\u002Fconfig\u002Fkibana.yml`][config-kbn].\n\nYou can also specify the options you want to override by setting environment variables inside the Compose file:\n\n```yml\nkibana:\n\n  environment:\n    SERVER_NAME: kibana.example.org\n```\n\nPlease refer to the following documentation page for more details about how to configure Kibana inside Docker\ncontainers: [Install Kibana with Docker][kbn-docker].\n\n### How to configure Logstash\n\nThe Logstash configuration is stored in [`logstash\u002Fconfig\u002Flogstash.yml`][config-ls].\n\nYou can also specify the options you want to override by setting environment variables inside the Compose file:\n\n```yml\nlogstash:\n\n  environment:\n    LOG_LEVEL: debug\n```\n\nPlease refer to the following documentation page for more details about how to configure Logstash inside Docker\ncontainers: [Configuring Logstash for Docker][ls-docker].\n\n### How to disable paid features\n\nYou can cancel an ongoing trial before its expiry date — and thus revert to a basic license — either from the [License\nManagement][license-mngmt] panel of Kibana, or using Elasticsearch's `start_basic` [Licensing API][license-apis]. Please\nnote that the second option is the only way to recover access to Kibana if the license isn't either switched to `basic`\nor upgraded before the trial's expiry date.\n\nChanging the license type by switching the value of Elasticsearch's `xpack.license.self_generated.type` setting from\n`trial` to `basic` (see [License settings][license-settings]) will only work **if done prior to the initial setup.**\nAfter a trial has been started, the loss of features from `trial` to `basic` _must_ be acknowledged using one of the two\nmethods described in the first paragraph.\n\n### How to scale out the Elasticsearch cluster\n\nFollow the instructions from the Wiki: [Scaling out Elasticsearch](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Fwiki\u002FElasticsearch-cluster)\n\n### How to re-execute the setup\n\nTo run the setup container again and re-initialize all users for which a password was defined inside the `.env` file,\nsimply \"up\" the `setup` Compose service again:\n\n```console\n$ docker compose up setup\n ⠿ Container docker-elk-elasticsearch-1  Running\n ⠿ Container docker-elk-setup-1          Created\nAttaching to docker-elk-setup-1\n...\ndocker-elk-setup-1  | [+] User 'monitoring_internal'\ndocker-elk-setup-1  |    ⠿ User does not exist, creating\ndocker-elk-setup-1  | [+] User 'beats_system'\ndocker-elk-setup-1  |    ⠿ User exists, setting password\ndocker-elk-setup-1 exited with code 0\n```\n\n### How to reset a password programmatically\n\nIf for any reason your are unable to use Kibana to change the password of your users (including [built-in\nusers][builtin-users]), you can use the Elasticsearch API instead and achieve the same result.\n\nIn the example below, we reset the password of the `elastic` user (notice \"\u002Fuser\u002Felastic\" in the URL):\n\n```sh\ncurl -XPOST -D- 'http:\u002F\u002Flocalhost:9200\u002F_security\u002Fuser\u002Felastic\u002F_password' \\\n    -H 'Content-Type: application\u002Fjson' \\\n    -u elastic:\u003Cyour current elastic password> \\\n    -d '{\"password\" : \"\u003Cyour new password>\"}'\n```\n\n## Extensibility\n\n### How to add plugins\n\nTo add plugins to any ELK component you have to:\n\n1. Add a `RUN` statement to the corresponding `Dockerfile` (eg. `RUN logstash-plugin install logstash-filter-json`)\n1. Add the associated plugin code configuration to the service configuration (eg. Logstash input\u002Foutput)\n1. Rebuild the images using the `docker compose build` command\n\n### How to enable the provided extensions\n\nA few extensions are available inside the [`extensions`](extensions) directory. These extensions provide features which\nare not part of the standard Elastic stack, but can be used to enrich it with extra integrations.\n\nThe documentation for these extensions is provided inside each individual subdirectory, on a per-extension basis. Some\nof them require manual changes to the default ELK configuration.\n\n## JVM tuning\n\n### How to specify the amount of memory used by a service\n\nThe startup scripts for Elasticsearch and Logstash can append extra JVM options from the value of an environment\nvariable, allowing the user to adjust the amount of memory that can be used by each component:\n\n| Service       | Environment variable |\n|---------------|----------------------|\n| Elasticsearch | ES_JAVA_OPTS         |\n| Logstash      | LS_JAVA_OPTS         |\n\nTo accommodate environments where memory is scarce (Docker Desktop for Mac has only 2 GB available by default), the Heap\nSize allocation is capped by default in the `docker-compose.yml` file to 512 MB for Elasticsearch and 256 MB for\nLogstash. If you want to override the default JVM configuration, edit the matching environment variable(s) in the\n`docker-compose.yml` file.\n\nFor example, to increase the maximum JVM Heap Size for Logstash:\n\n```yml\nlogstash:\n\n  environment:\n    LS_JAVA_OPTS: -Xms1g -Xmx1g\n```\n\nWhen these options are not set:\n\n* Elasticsearch starts with a JVM Heap Size that is [determined automatically][es-heap].\n* Logstash starts with a fixed JVM Heap Size of 1 GB.\n\n### How to enable a remote JMX connection to a service\n\nAs for the Java Heap memory (see above), you can specify JVM options to enable JMX and map the JMX port on the Docker\nhost.\n\nUpdate the `{ES,LS}_JAVA_OPTS` environment variable with the following content (I've mapped the JMX service on the port\n18080, you can change that). Do not forget to update the `-Djava.rmi.server.hostname` option with the IP address of your\nDocker host (replace **DOCKER_HOST_IP**):\n\n```yml\nlogstash:\n\n  environment:\n    LS_JAVA_OPTS: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=18080 -Dcom.sun.management.jmxremote.rmi.port=18080 -Djava.rmi.server.hostname=DOCKER_HOST_IP -Dcom.sun.management.jmxremote.local.only=false\n```\n\n## Going further\n\n### Plugins and integrations\n\nSee the following Wiki pages:\n\n* [External applications](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Fwiki\u002FExternal-applications)\n* [Popular integrations](https:\u002F\u002Fgithub.com\u002Fdeviantony\u002Fdocker-elk\u002Fwiki\u002FPopular-integrations)\n\n[elk-stack]: https:\u002F\u002Fwww.elastic.co\u002Felastic-stack\u002F\n[elastic-docker]: https:\u002F\u002Fwww.docker.elastic.co\u002F\n[subscriptions]: https:\u002F\u002Fwww.elastic.co\u002Fsubscriptions\n[es-security]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Freference\u002Felasticsearch\u002Fconfiguration-reference\u002Fsecurity-settings\n[license-settings]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Freference\u002Felasticsearch\u002Fconfiguration-reference\u002Flicense-settings\n[license-mngmt]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fdeploy-manage\u002Flicense\u002Fmanage-your-license-in-self-managed-cluster\n[license-apis]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fapi\u002Fdoc\u002Felasticsearch\u002Fgroup\u002Fendpoint-license\n\n[docker-install]: https:\u002F\u002Fdocs.docker.com\u002Fget-started\u002Fget-docker\u002F\n[compose-install]: https:\u002F\u002Fdocs.docker.com\u002Fcompose\u002Finstall\u002F\n[linux-postinstall]: https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Finstall\u002Flinux-postinstall\u002F\n[desktop-filesharing]: https:\u002F\u002Fdocs.docker.com\u002Fdesktop\u002Fsettings-and-maintenance\u002Fsettings\u002F#file-sharing\n\n[bootstrap-checks]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fdeploy-manage\u002Fdeploy\u002Fself-managed\u002Fbootstrap-checks\n[es-sys-config]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fdeploy-manage\u002Fdeploy\u002Fself-managed\u002Fimportant-system-configuration\n[es-heap]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fdeploy-manage\u002Fdeploy\u002Fself-managed\u002Fimportant-settings-configuration#heap-size-settings\n\n[builtin-users]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fdeploy-manage\u002Fusers-roles\u002Fcluster-or-deployment-auth\u002Fbuilt-in-users\n[ls-monitoring]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Freference\u002Flogstash\u002Fmonitoring-with-metricbeat\n[sec-cluster]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fdeploy-manage\u002Fsecurity#cluster-or-deployment-security-features\n\n[config-es]: .\u002Felasticsearch\u002Fconfig\u002Felasticsearch.yml\n[config-kbn]: .\u002Fkibana\u002Fconfig\u002Fkibana.yml\n[config-ls]: .\u002Flogstash\u002Fconfig\u002Flogstash.yml\n\n[es-docker]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fdeploy-manage\u002Fdeploy\u002Fself-managed\u002Finstall-elasticsearch-with-docker\n[kbn-docker]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fdeploy-manage\u002Fdeploy\u002Fself-managed\u002Finstall-kibana-with-docker\n[ls-docker]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Freference\u002Flogstash\u002Fdocker-config\n\n[upgrade]: https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fdeploy-manage\u002Fupgrade\u002Fdeployment-or-cluster\u002Fself-managed\n\n\u003C!-- markdownlint-configure-file\n{\n  \"MD033\": {\n    \"allowed_elements\": [ \"picture\", \"source\", \"img\" ]\n  }\n}\n-->\n","该项目提供了一个基于Docker和Docker Compose的Elastic Stack（ELK）环境，方便用户快速搭建并运行。它集成了Elasticsearch、Logstash和Kibana三大组件，利用Elasticsearch的强大搜索与聚合能力以及Kibana的数据可视化功能，帮助分析各类数据集。项目基于官方提供的Docker镜像构建，并支持TLS加密等高级特性。尽管其设计初衷并非直接用于生产环境部署，但非常适合作为开发测试阶段或学习探索ELK生态系统的工具使用。",2,"2026-06-11 03:25:49","top_topic"]