# ELK Cluster Design **URL:** \ **Category:** Elasticsearch\ **Created:** [January 7, 2016, 1:14pm UTC](https://discuss.elastic.co/t/elk-cluster-design/38617 "2016-01-07T13:14:30Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![fir3wall](https://avatars.discourse-cdn.com/v4/letter/f/df788c/32.png) [@fir3wall](https://discuss.elastic.co/u/fir3wall)\ **Post date:** [January 7, 2016, 1:14pm UTC](https://discuss.elastic.co/t/elk-cluster-design/38617/1 "2016-01-07T13:14:30Z")
Hello, I'm trying to design a POC for my boss. I've got client at remote location who will need to feed our new elastic cluster in cloud. Currently I've got: - Client Side :: Redis (queue) -\> Logstash - Cloud Side :: 3 x Elastic machines in cluster + 1 small VM with Kibana Data will go over Site to Site VPN . My question is do I need another Logstash in my cloud to receive this data and forward to cluster or I can directly feed it to my cluster - I know both solutions will work just wonder what is best practice In addition can I stick another Elasticsearch instance on cilent side to agregate data on cliend side and then send it to my cloud cluster? Our development team proposed this as way to maybe reduce the network traffic etc (if we can send ready data to cluster). Thanks D ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 8, 2016, 4:05am UTC](https://discuss.elastic.co/t/elk-cluster-design/38617/2 "2016-01-08T04:05:44Z")
I'd have a LS + broker instance setup in the remote site, so that if the link goes down you can queue things up there. Putting an ES instance won't do much. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:26pm UTC](https://discuss.elastic.co/t/elk-cluster-design/38617/3 "2017-07-05T23:26:13Z")