Generate Kibana encryption keys on startup#18
Open
smith wants to merge 2 commits into
Open
Conversation
Replaces hardcoded encryption keys with dynamically generated ones. A new setup_kibana_keys service generates three 32-char hex keys on first run and persists them on the etc volume. Kibana merges the generated keys into its config at startup. Closes #6 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Replace `cat /dev/urandom | tr | head` pipeline with `dd | xxd` to avoid SIGPIPE exit code 141 when used with `set -eo pipefail`. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
config/kibana.ymlscripts/generate-kibana-keys.shthat generates three 32-character hex keys on first runsetup_kibana_keysservice that runs before Kibana startsetcDocker volume across restartsCloses #6
Test plan
docker compose down -v && docker compose up— verify Kibana starts successfullydocker compose logs setup_kibana_keys— should show "Kibana encryption keys generated"docker compose restart kibana— should reuse existing keys (no regeneration)🤖 Generated with Claude Code