New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3: custom s3 endpoint #181

Closed
l15k4 opened this Issue Feb 11, 2017 · 6 comments

Comments

Projects
None yet
7 participants
@l15k4

l15k4 commented Feb 11, 2017

Hey,

I'm using https://github.com/jubos/fake-s3 extensively in many projects and I'm very satisfied with it so far.
It requires the aws s3 client to be set with :

s3.setEndpoint(s"http://localhost:1234")
s3.setS3ClientOptions(S3ClientOptions.builder().setPathStyleAccess(true).disableChunkedEncoding().build())

for it to work. At least the endpoint, the second setting is not necessary. Is there a way to change endpoint without changing code? It is not possible with the proxy

@ktoso ktoso added the help wanted label May 10, 2017

@raboof raboof added the p:aws-s3 label Jul 12, 2017

@francisdb

This comment has been minimized.

Show comment
Hide comment
@francisdb

francisdb Jul 12, 2017

Contributor

Interesting, I wonder if there is a similar project for the jvm

Contributor

francisdb commented Jul 12, 2017

Interesting, I wonder if there is a similar project for the jvm

@carstenlenz

This comment has been minimized.

Show comment
Hide comment
@carstenlenz

carstenlenz Aug 17, 2017

We use https://github.com/findify/s3mock
Sadly there are some issues with Alpakka S3 and S3Mock.

carstenlenz commented Aug 17, 2017

We use https://github.com/findify/s3mock
Sadly there are some issues with Alpakka S3 and S3Mock.

@l15k4

This comment has been minimized.

Show comment
Hide comment
@l15k4

l15k4 Aug 17, 2017

Yeah, I've been using both. But I'm way more productive with fake-s3, s3mock had too many issues, fake-s3 is almost flawless for testing purposes.

l15k4 commented Aug 17, 2017

Yeah, I've been using both. But I'm way more productive with fake-s3, s3mock had too many issues, fake-s3 is almost flawless for testing purposes.

@ennru

This comment has been minimized.

Show comment
Hide comment
@ennru

ennru Jan 3, 2018

Member

The work of #619 is now continued in #677

Member

ennru commented Jan 3, 2018

The work of #619 is now continued in #677

@easel

This comment has been minimized.

Show comment
Hide comment
@easel

easel Jan 3, 2018

Contributor

For reference, there is a (passing) integration test in #677 that uses custom endpoints to connect to minio (https://www.minio.io), including a one-liner to set up and configure minio for testing using docker. From what I can tell it's a fairly complete s3 implementation and worked as expected after I made a tweak to the url encoding of paths.

Contributor

easel commented Jan 3, 2018

For reference, there is a (passing) integration test in #677 that uses custom endpoints to connect to minio (https://www.minio.io), including a one-liner to set up and configure minio for testing using docker. From what I can tell it's a fairly complete s3 implementation and worked as expected after I made a tweak to the url encoding of paths.

@ennru ennru added this to the 0.16 milestone Jan 9, 2018

@ennru

This comment has been minimized.

Show comment
Hide comment
@ennru

ennru Jan 9, 2018

Member

Fixed with #677

Member

ennru commented Jan 9, 2018

Fixed with #677

@ennru ennru closed this Jan 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment