NETWAYS / NETWAYS/ansible-collection-elasticstack
Re-enable encrypted TLS keys for Logstash Beats input
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
In #46 we had to disable encryption for TLS keys for the Beats input of Logstash. We went through a lot of different combinations of Logstash, Beats plugin and JRE but we couldn't find a reliabe combination that will work.
So I'm opening this issue so that we don't forget to re-enable if the future brings reliable combinations. (And to have a link to the removed code in case we can re-use it)
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 reviewing issue #46 and the change that removed encrypted TLS-key support. Research currently reliable combinations of Logstash, its Beats plugin, and the JRE, then verify that encryption can be re-enabled without the compatibility failures described here. Done means encrypted TLS keys work reliably for the Beats input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, java
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100