# Installing and using logstash (and other elk components) with plugins on a shared mount **URL:** \ **Category:** Logstash\ **Created:** [June 23, 2017, 9:57am UTC](https://discuss.elastic.co/t/installing-and-using-logstash-and-other-elk-components-with-plugins-on-a-shared-mount/90608 "2017-06-23T09:57:54Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)\ **Post date:** [June 29, 2017, 9:45am UTC](https://discuss.elastic.co/t/installing-and-using-logstash-and-other-elk-components-with-plugins-on-a-shared-mount/90608/3 "2017-06-29T09:45:24Z")
This might work. Follow these some or all of [these instructions](https://discuss.elastic.co/t/solved-multiple-instances-for-logstash/65539/2). The instructions are how to run multiple Debian services as separate LS instances from one installation. You will not need to do the last bit i.e. from `plus SERVICE_NAME and SERVICE_DESCRIPTION` onward. Remember to use local disk for the LS data and log folders. Config can be on the shared mount but keep separate. Also, check that `bin/logstash.lib.sh` is detecting the shared mount paths in the local context correctly. Good luck - to my knowledge this has never been tried. OTOH - why not use Ansible, Chef or Puppet to install a preloaded copy of LS? --- _[View the full topic](https://discuss.elastic.co/t/installing-and-using-logstash-and-other-elk-components-with-plugins-on-a-shared-mount/90608)._