# Sending Beat data from AWS to a server with a private IP
**URL:** https://discuss.elastic.co/t/sending-beat-data-from-aws-to-a-server-with-a-private-ip/81750
**Category:** Beats
**Tags:** winlogbeat
**Created:** [April 10, 2017, 6:55am UTC](https://discuss.elastic.co/t/sending-beat-data-from-aws-to-a-server-with-a-private-ip/81750 "2017-04-10T06:55:48Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@onlybalu](https://discuss.elastic.co/u/onlybalu)
#### Post date: [April 10, 2017, 6:55am UTC](https://discuss.elastic.co/t/sending-beat-data-from-aws-to-a-server-with-a-private-ip/81750/1 "2017-04-10T06:55:48Z")
Hi Team,
I am new to this, Need to get the Windows Event Logs from AWS cloud to my VMware Ubuntu Logstash server.
I am not able to connect to my Ubuntu Logstash server (private ip) from an AWS Windows cloud instance (public ip).
- Logstash IP is private ip
- AWS cloud ip is public ip
We created the rule in my firewall ( allow the 5044 port from publicly ) for log receive.
Find below my configuration:
```auto
winlogbeat.event_logs:
- name: Security
ignore_older: 2h
event_id: 4727, 4731, 4754, 4726
- name: Application
ignore_older: 2h
- name: Security
ignore_older: 2h
output.logstash:
hosts: ["192.168.6.103:5044"]
bulk_max_size: 1024
index: winlogbeat
ssl:
certificate_authorities: ["C:/ProgramData/winlogbeat/logstash-forwarder.crt"]
logging.to_files: true
logging.files:
path: C:/ProgramData/winlogbeat/Logs
logging.level: debug
```
Below find the error from Winlogbeat (AWS instance windows 2008 r2 server) .
`2017-04-10T02:58:50+01:00 ERR Connecting error publishing events (retrying): dial tcp 192.168.6.103:5044: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 2017-04-10T02:58:50+01:00 DBG send fail`
Its urgent your previous post was nice,
Thanks,
Balasubramaniam.A.G
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [April 10, 2017, 9:13am UTC](https://discuss.elastic.co/t/sending-beat-data-from-aws-to-a-server-with-a-private-ip/81750/2 "2017-04-10T09:13:16Z")
This is not a beats problem, this is a networking issue.
Unless you can provide a way for the Azure host to reach into that local network, you won't get anywhere.
---
### Author:  [@onlybalu](https://discuss.elastic.co/u/onlybalu)
#### Post date: [April 10, 2017, 9:17am UTC](https://discuss.elastic.co/t/sending-beat-data-from-aws-to-a-server-with-a-private-ip/81750/3 "2017-04-10T09:17:26Z")
Hi Warkolm,
Thanks for your reply, It will work only Azure host, not in AWS host?
Will it work only azure?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [April 10, 2017, 9:58am UTC](https://discuss.elastic.co/t/sending-beat-data-from-aws-to-a-server-with-a-private-ip/81750/4 "2017-04-10T09:58:07Z")
I meant AWS sorry.
---
### Author:  [@onlybalu](https://discuss.elastic.co/u/onlybalu)
#### Post date: [April 10, 2017, 10:06am UTC](https://discuss.elastic.co/t/sending-beat-data-from-aws-to-a-server-with-a-private-ip/81750/5 "2017-04-10T10:06:42Z")
Hi Warkolm,
Thanks for your reply,
I assume that it was a network issue, Please suggest me, What can i do for the network?
what is the way to resolve my network issue? once i resolved, I put the server in production in my office.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [April 10, 2017, 10:07am UTC](https://discuss.elastic.co/t/sending-beat-data-from-aws-to-a-server-with-a-private-ip/81750/6 "2017-04-10T10:07:30Z")
A VPN may solve it.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 8, 2017, 10:22am UTC](https://discuss.elastic.co/t/sending-beat-data-from-aws-to-a-server-with-a-private-ip/81750/7 "2017-05-08T10:22:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.