# Connect to Cloud Elastic / Cloud Elasticsearch instance with ssh **URL:** \ **Category:** Elasticsearch\ **Created:** [December 12, 2017, 8:06am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266 "2017-12-12T08:06:39Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Milad\_Hamid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milad_hamid/32/24327_2.png) [@Milad\_Hamid](https://discuss.elastic.co/u/Milad_Hamid)\ **Post date:** [December 12, 2017, 8:06am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/1 "2017-12-12T08:06:39Z")
Hi, How i can connect to my Cloud Elastic trial with ssh or WinSCP? so i can install Logstash and manage directories. ---
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [December 12, 2017, 8:15am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/2 "2017-12-12T08:15:53Z")
This is not available. Elastic Cloud only supports launching Elasticsearch clusters and Kibana instances and there is no way to ssh into the hosts. ---
**Author:** ![Milad\_Hamid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milad_hamid/32/24327_2.png) [@Milad\_Hamid](https://discuss.elastic.co/u/Milad_Hamid)\ **Post date:** [December 12, 2017, 8:18am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/3 "2017-12-12T08:18:28Z")
@thiago, ok so it is same as Amazon Elasticsearch service Thanks for quick reply ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 12, 2017, 8:30am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/4 "2017-12-12T08:30:30Z")
> it is same as Amazon Elasticsearch service If you meant to say that [cloud.elastic.co](http://cloud.elastic.co) is the same as Amazon Elasticsearch service, I'd definitely say "no". If you meant that you can not run LS for now on both Amazon Elasticsearch service and Cloud by elastic, yes you're right. ---
**Author:** ![Milad\_Hamid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milad_hamid/32/24327_2.png) [@Milad\_Hamid](https://discuss.elastic.co/u/Milad_Hamid)\ **Post date:** [December 12, 2017, 8:34am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/5 "2017-12-12T08:34:03Z")
Thanks @dadoonet, yes exactly that what i meant, running LS on both. Because right now that means i need to run Logstash on a separate server, so we need two servers to implement our ELK - Logging system. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 12, 2017, 8:45am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/6 "2017-12-12T08:45:57Z")
Is the LS pipeline a bit complex? Or using multiple outputs? If not, may be have a look at ingest node feature. ---
**Author:** ![Milad\_Hamid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milad_hamid/32/24327_2.png) [@Milad\_Hamid](https://discuss.elastic.co/u/Milad_Hamid)\ **Post date:** [December 12, 2017, 9:34am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/7 "2017-12-12T09:34:30Z")
Actually using multiple inputs and outputs. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 12, 2017, 5:09pm UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/8 "2017-12-12T17:09:08Z")
Ha right. Then you need LS indeed. ---
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [December 12, 2017, 11:48pm UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/9 "2017-12-12T23:48:44Z")
But keep in mind that running LS on the same server as an Elasticsearch node is not a recommended production deployment anyway. It doesn't matter if it's AWS ES or our Elastic Cloud or simply a cluster managed by you, running LS on separate servers is the way to go for production deployment of the Stack. ---
**Author:** ![Milad\_Hamid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milad_hamid/32/24327_2.png) [@Milad\_Hamid](https://discuss.elastic.co/u/Milad_Hamid)\ **Post date:** [December 13, 2017, 8:53am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/10 "2017-12-13T08:53:08Z")
Yes @thiago actually we are planning to have LS on a separate server to implement our ELK - Logging System ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 10, 2018, 8:53am UTC](https://discuss.elastic.co/t/connect-to-cloud-elastic-cloud-elasticsearch-instance-with-ssh/111266/11 "2018-01-10T08:53:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.