allow --endpoint-url option to work with S3 compatible services
rmanus opened this issue · 7 comments
It is currently not possible to use s3p with non AWS S3 compatible services.
I also had this problem, I added this at line 59 of s3p/source/S3Parallel/Lib/S3.js
and it worked.
In my case I'm using Wasabi instead of AWS S3 but you can fill in your desired endpoint of course.
this.wasabiEndpoint = new (require("aws-sdk").Endpoint)("https://s3.us-west-1.wasabisys.com");
this.awsSdkS3 = new (require("aws-sdk").S3)({endpoint: this.wasabiEndpoint});
Good idea! I'll look into adding it. I think just --endpoint [url]
will suffice.
This would be a really useful feature for us as it enables us to use this in other S3 implementations such as Ceph. Any idea if and possibly when this could be available?
Hi, is there any update if the --endpoint flag will be added?
I would also like to have this.
I also had this problem, I added this at line 59 of
s3p/source/S3Parallel/Lib/S3.js
and it worked. In my case I'm using Wasabi instead of AWS S3 but you can fill in your desired endpoint of course.this.wasabiEndpoint = new (require("aws-sdk").Endpoint)("https://s3.us-west-1.wasabisys.com"); this.awsSdkS3 = new (require("aws-sdk").S3)({endpoint: this.wasabiEndpoint});
in which function should I add this? Sorry I don't know much of JS but I really need to use this on wasabi as well, I think line 59 is not the same anymore
Not supporting custom api endpoint kill any usage of self-hosted aws s3, e.g. localstack.