I would like to setup a system in which a anycodings_elasticsearch developer logs into a secured internal anycodings_elasticsearch service, asks for a token, and start anycodings_elasticsearch streaming logs from her/his workstation anycodings_elasticsearch right away. I'm setting up a centralized ELK stack for anycodings_elasticsearch log analytics that will be used to collect anycodings_elasticsearch logs from a variety of different systems, anycodings_elasticsearch some may be actual servers, most will be anycodings_elasticsearch developer's workstations. I am also aware that it is possible to anycodings_elasticsearch secure the logstash -> elastic anycodings_elasticsearch connection with API keys, but that's not anycodings_elasticsearch what I need, I need securing from filebeat anycodings_elasticsearch to logstash.
![elk stack filebeats bro flow diagram elk stack filebeats bro flow diagram](https://venturebeat.com/wp-content/uploads/2018/09/snapdragon-3100.png)
![elk stack filebeats bro flow diagram elk stack filebeats bro flow diagram](https://venturebeat.com/wp-content/uploads/2018/09/Close-up-shot-of-DON-system-and-Kuka-Robot-grasping-a-cup.jpg)
I know that it is possible to secure the anycodings_elasticsearch filebeat -> logstash connection through anycodings_elasticsearch HTTPS mutual authentication, but I feel they anycodings_elasticsearch are pretty hard to manage if we have many anycodings_elasticsearch different filebeat clients (prove me wrong anycodings_elasticsearch and I'll happily change my mind). Is it possible to secure the communication anycodings_elasticsearch between filebeat and logstash with a token anycodings_elasticsearch of some kind?