Skip to content

docs: document elasticsearch.yml location for xpack.security - #40

Open
vee1e wants to merge 2 commits into
certego:masterfrom
vee1e:docs/elasticsearch-yml-location-34
Open

vee1e wants to merge 2 commits into
certego:masterfrom
vee1e:docs/elasticsearch-yml-location-34

Conversation

@vee1e

@vee1e vee1e commented Aug 25, 2026

Copy link
Copy Markdown

Fixes #34

This adds the missing answer for where to put elasticsearch.yml when you want to turn on security. By default PcapMonkey does not ship that file. The search service runs from a Docker image with its config inside the container.

What changed:

  • README now shows how to create config/elasticsearch/elasticsearch.yml, with the three defaults the image expects plus xpack.security.enabled. Mounting a file with only the last line hides the defaults and the service may not start.
  • Notes that the file must exist before you start the stack, otherwise Docker makes a folder with that name.
  • Shows the mount in the right place under the search service, keeping the data folder.
  • Restart now covers the whole stack, and warns that turning on security without a password breaks the log shippers that talk to the search service.
  • Includes the no-file alternative using an environment setting, and notes the ARM image tag differs.

vee1e added 2 commits August 25, 2026 22:01
…ix mount/restart (fixes certego#34)

- preserve cluster.name/network.host when mounting elasticsearch.yml
- add mkdir -p and chmod, note file must exist before up
- warn that enabling xpack breaks filebeat/kibana without password
- show volumes under services.elasticsearch.volumes
- fix restart to whole stack and env var example in context
- note 7.17.28 vs 7.17.28-arm64
@CLAassistant

CLAassistant commented Aug 25, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Where is elasticsearch.yml

2 participants