NETWAYS / NETWAYS/ansible-collection-elasticstack
[Feature]: Logstash — opt-in client certificate to Elasticsearch (mTLS), split from cacert/auth
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
The Logstash ES output (elasticsearch-output.conf.j2) bundles keystore (client cert), cacert (server verification) and user/password (auth) under one flag — and the keystore is shipped even though ES does not request a client cert, so it is ignored today.
Separate the concerns: cacert / ssl_certificate_authorities (the client verifying the ES server — needed for any TLS, docs) stays on the TLS axis; the keystore / ssl_keystore_path (Logstash's own client certificate) becomes an opt-in mTLS flag.
Depends on: the ES-side enabler xpack.security.http.ssl.client_authentication (#536) and the Logstash TLS axis logstash_tls (#529). Overlaps #529 — both restructure the same ES-output block, so coordinate. Opt-in, default off. Part of #536. 2.0.0.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with elasticsearch-output.conf.j2 and compare the Logstash TLS axis in #529 with the Elasticsearch-side client-authentication setting in #536. Done means the keystore/ssl_keystore_path is controlled by a separate opt-in mTLS flag, while cacert/ssl_certificate_authorities remains on the TLS axis and mTLS defaults off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100