Highlighted
2 Bronze

S3 interface to ATMOS using jets3t

I have an app that interfaces with different cloud storage devices. It uses S3 and jets3t-0.6.1.jar to talk to Amazon. Using the same interface I like to talk to ATMOS but no matter what properties I set for the org.jets3t.service.impl.rest.httpclient.RestS3Service, it always goes to s3.amazonaws.com instead of the ATMOS host that I have specified. The logs collected show that when I send to Amazon and ATMOS, the two URLs used are different: Amazon: org.jets3t.service.impl.rest.httpclient.RestS3Service.performRequest(RestS3Service.java:334)          "Performing PUT request for 'https://MYBUCKET.s3.amazonaws.com/8e3c3d97-0c2f-42bb-aee7-2b1674bb439b', expecting response code 200" ATMOS: org.jets3t.service.impl.rest.httpclient.RestS3Service.performRequest(RestS3Service.java:334)          "Performing PUT request for 'https://s3.amazonaws.com/CASBucket/ba9ec436-f467-402f-9b51-dbf490260cca', expecting response code 200" Right before issuing the “myRestS3Service.putObject(bucket, s3obj);” I print all the properties of myRestS3Service and they are what I expect (i.e. my ATMOS host and port are there and no reference to s3.amazonaws.com). I have experimented with a variety of combinations of these properties: httpclient.proxy-autodetect=true; httpclient.proxy-host=HOST; httpclient.proxy-port=PORT; s3service.s3-endpoint=HOST; s3service.s3-endpoint-http-port=PORT; s3service.s3-endpoint-https-port=PORT; s3service.disable-dns-buckets=false; s3service.https-only=true; Has anyone had success with jets3t with ATMOS?

Labels (1)
0 Kudos
Reply
2 Replies
Highlighted
2 Bronze

Sorry, the formatting was lost, not sure why.

0 Kudos
Reply
Highlighted
2 Bronze

FYI, using a newer version of jets3t resolved the issue. See this for more details:

https://groups.google.com/forum/#!topic/jets3t-users/38--nnMvwGk

0 Kudos
Reply