Hi All, Could you please help with the below NLB configuration in AWS in-front of FileBeat Instance? When I tried to created the setup, the Target Group always shows unhealthy - Health checks failed. Requirement: 1. Devices(over UDP) --> 2.NLB --> 3.FileBeat Server (EC2) --> AWS MSK --> LogStash …

I think that your problem is that the AWS NLB can't do a health check using UDP, so you will need to do the health check using TCP or HTTP/HTTPS. You can do that adding a TCP input that will be used only for this healthcheck, than in your target group you configure the health check to use this port…

Health Check on FileBeats Instance from AWS NLB

Elastic Stack Beats

warkolm (Mark Walkom) April 6, 2021, 9:50pm 3

Please don't create multiple topics for the same question, let's continue the discussion in your original thread AWS NLB config infront of FileBeats Instance

Topic		Replies	Views
AWS NLB config infront of FileBeats Instance Beats filebeat	7	849	May 6, 2021
Logstash 2.1.1 behind ELB Logstash	4	1791	July 6, 2017
Filebeats logs -> aws elb of logstash Beats filebeat	5	3399	January 11, 2018
Same HTTP health check succeeds for ALB and failes for NLB Logstash	5	3270	June 22, 2018
Filebeat AWS Module & ELB fileset, got error in parsing NLB log Beats filebeat	1	428	December 30, 2020

Health Check on FileBeats Instance from AWS NLB

Related topics