# Loading Logstash pipeline from a central source (perhaps via HTTP)?

**URL:** <https://discuss.elastic.co/t/loading-logstash-pipeline-from-a-central-source-perhaps-via-http/82174>\
**Category:** Logstash\
**Created:** [April 12, 2017, 1:59pm UTC](https://discuss.elastic.co/t/loading-logstash-pipeline-from-a-central-source-perhaps-via-http/82174 "2017-04-12T13:59:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rcowart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rcowart/32/88091_2.png) [@rcowart](https://discuss.elastic.co/u/rcowart)\
**Post date:** [April 12, 2017, 1:59pm UTC](https://discuss.elastic.co/t/loading-logstash-pipeline-from-a-central-source-perhaps-via-http/82174/1 "2017-04-12T13:59:05Z")

</div>

I am looking for ideas on how to easily spin up multiple Logstash instances from a common pipeline config source. Ideally I would be able to specify a URL (e.g. S3 bucket), instead of a local file or directory, from which logstash would fetch the pipeline and load. I could probably just read-only mount an NFS share where the files reside, but that doesn't seem particularly elegant.

I am curious what others may be doing.

Thanks,

Rob

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [April 12, 2017, 2:15pm UTC](https://discuss.elastic.co/t/loading-logstash-pipeline-from-a-central-source-perhaps-via-http/82174/2 "2017-04-12T14:15:41Z")

</div>

This is a feature coming to Logstash in a future release.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 10, 2017, 2:19pm UTC](https://discuss.elastic.co/t/loading-logstash-pipeline-from-a-central-source-perhaps-via-http/82174/3 "2017-05-10T14:19:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
