NETWAYS / NETWAYS/ansible-collection-elasticstack
[Feature]: Beats — opt-in client certificate to Elasticsearch (mTLS)
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
Beats currently present a client certificate only to Logstash (Logstash enforces it with ssl_verify_mode => force_peer), not to Elasticsearch — so beats→ES is one-way TLS + password.
Add an opt-in that makes Beats present a client certificate on the Elasticsearch output (ssl.certificate + ssl.key), for mutual TLS. ssl.certificate_authorities (server verification) is unchanged and stays on the TLS side.
Depends on: the ES-side enabler xpack.security.http.ssl.client_authentication (see #536 — else ES ignores the cert) and the Beats TLS axis beats_tls (#528). 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 by tracing the Beats Elasticsearch output configuration and the TLS settings referenced by beats_tls (#528), then review the ES-side client-authentication dependency in #536. Done means an opt-in default-off setting sends ssl.certificate and ssl.key to Elasticsearch for mTLS while leaving ssl.certificate_authorities unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100