Filebeat is developed in Go language and there is no dependency of java to deploy it either by source code or by rpm.
As Filebeat is very lightweight process, so there is no such minimum hardware requirement of filebeat is there as per elastic.co.
But I gathered few information just before and after installation of filebeat and I found it takes Memory : approx 1810 kB CPU usage : very very little.
To get more info regarding CPU or Memory usage you can use "vmstat", "iostat", "/proc/meminfo" before and after service start or installation of filebeat
Filebeat uses back-pressure protocol to handle the heavy load of logs. To handle this Filebeat spooler and harvester will use more memory and cpu . So system utilization will be increased accordingly. But it totally use case specific.