Filebeat : Badly Stuck with Connection reset by peer error

As per @tomwj post Elasitcsearch-ruby raises "Cannot get new connection from pool" error

I tried by removing sniffing => true.

I'm able to insert data to elastic search by using nc command through tcp 5044 port with below config.

[ec2-user@ip-10-3-1-13 conf.d]$ nc elk_server_ip.compute-1.amazonaws.com 5044
jashwanth
dsjdskadjasdhskadf
asfjkdsfhdsfkf
fskjhasfkjfs
asfjkfashsaf
khfdslaf

Config for testing:

input {
tcp {
port => 5044
}
}

So, there is no issues with logstash and ES end now.

Still able to see below error in filebeat end and suspecting the logs are not reaching logstash from filebeat.

2016-11-22T18:32:22Z DBG Try to publish 932 events to logstash with window size 1
2016-11-22T18:32:22Z DBG close connection
2016-11-22T18:32:22Z DBG 0 events out of 932 events sent to logstash. Continue sending ...
2016-11-22T18:32:22Z INFO Error publishing events (retrying): EOF
2016-11-22T18:32:22Z INFO send fail
2016-11-22T18:32:22Z INFO backoff retry: 1m0s