# Using envoy proxy to create S3 endpoint

**URL:** <https://discuss.elastic.co/t/using-envoy-proxy-to-create-s3-endpoint/341239>\
**Category:** Community Ecosystem\
**Tags:** snapshot-and-restore\
**Created:** [August 21, 2023, 12:46pm UTC](https://discuss.elastic.co/t/using-envoy-proxy-to-create-s3-endpoint/341239 "2023-08-21T12:46:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![subhashmk](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@subhashmk](https://discuss.elastic.co/u/subhashmk)\
**Post date:** [August 21, 2023, 12:46pm UTC](https://discuss.elastic.co/t/using-envoy-proxy-to-create-s3-endpoint/341239/1 "2023-08-21T12:46:58Z")

</div>

In elasticsearch snapshot repo, instead of specifying main S3 endpoint, we have added new envoy proxy sidecar to take care of authentication. Envoy proxy container will add authentication to incoming request and forward that request to S3 endpoint. That's why we are specifying new local envoy proxy endpoint (localhost:15670) in elasticsearch snapshot repository config. But while creating snapshot repository, we are getting error "backup path is not accessible on master node". What could be the issue? What needs to be done to fix this?

---

<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:** [September 18, 2023, 12:47pm UTC](https://discuss.elastic.co/t/using-envoy-proxy-to-create-s3-endpoint/341239/2 "2023-09-18T12:47:34Z")

</div>

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