Because Packetbeat needs to capture network packets from a raw socket, it needs root permissions to open the socket. You can make it drop privileges after opening the socket, similar to apache, not sure if that is enough in your case.
You should be able to do this by giving the packetbeat binary CAP_NET_RAWcapability.
$ sudo setcap cap_net_raw=ep /usr/bin/packetbeat
After that you can start packetbeat as any user. This will not work in a nosuid mount (e.g. Ubuntu home directory), but /usr/bin should be fine. I'm pretty sure systemd can set process capabilities too, and that might be the most acceptable solution for your sysadmins.
It doesn't matter under which account Apache, ES or Redis are running. Packetbeat sees all the network packets on the machine it runs on.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.