# S3 compatible storage

**URL:** <https://discourse.nodered.org/t/s3-compatible-storage/62467>\
**Category:** Developing Nodes\
**Created:** [10 May 2022 17:46 UTC](https://discourse.nodered.org/t/s3-compatible-storage/62467 "2022-05-10T17:46:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Miguel](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/miguel/32/61392_2.png) [@Miguel](https://discourse.nodered.org/u/Miguel)\
**Post date:** [10 May 2022 17:46 UTC](https://discourse.nodered.org/t/s3-compatible-storage/62467/1 "2022-05-10T17:46:58Z")

</div>

I've searched a lot but couldn't find the right node to connect to a non-aws s3 compatible storage.

Would it be possible to give an option to specify the endpoint being able to use S3 compatible storage, and not only aws s3 ?  
REST Endpoint Example: [rest.server.com:8080](http://rest.server.com:8080)

All aws s3 related nodes I've found are predefined for aws.

---

<div class="post-metadata">

**Author:** ![craigcurtin](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@craigcurtin](https://discourse.nodered.org/u/craigcurtin)\
**Post date:** [10 May 2022 22:25 UTC](https://discourse.nodered.org/t/s3-compatible-storage/62467/2 "2022-05-10T22:25:11Z")

</div>

Couldnt you just fork one of the AWS nodes and change the hard coded naming to whatever you want ? or better still make it a config option ??

Craig

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [9 July 2022 22:26 UTC](https://discourse.nodered.org/t/s3-compatible-storage/62467/3 "2022-07-09T22:26:11Z")

</div>

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