# Support for alternate 'endpoint' and 'protocol' parameters in Logstash S3 output plugin?

**URL:** <https://discuss.elastic.co/t/support-for-alternate-endpoint-and-protocol-parameters-in-logstash-s3-output-plugin/155047>\
**Category:** Logstash\
**Created:** [November 1, 2018, 4:26pm UTC](https://discuss.elastic.co/t/support-for-alternate-endpoint-and-protocol-parameters-in-logstash-s3-output-plugin/155047 "2018-11-01T16:26:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tad](https://avatars.discourse-cdn.com/v4/letter/t/278dde/32.png) [@tad](https://discuss.elastic.co/u/tad)\
**Post date:** [November 1, 2018, 4:26pm UTC](https://discuss.elastic.co/t/support-for-alternate-endpoint-and-protocol-parameters-in-logstash-s3-output-plugin/155047/1 "2018-11-01T16:26:21Z")

</div>

I'm hoping to find out if there's any support for specifying an alternate 'endpoint' and 'protocol' in the Logstash S3 output plugin, similar to what is provided in the following S3 Repository plugin?

We have an internal S3-compliant object storage service that we'd like to direct Logstash output to but I have not been successful in specifying an alternate endpoint in the output parameters in logstash.yml. Looks like the basic AWS S3 regions are only accepted.

---

<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:** [November 29, 2018, 4:26pm UTC](https://discuss.elastic.co/t/support-for-alternate-endpoint-and-protocol-parameters-in-logstash-s3-output-plugin/155047/2 "2018-11-29T16:26:38Z")

</div>

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