On Fri, Apr 13, 2018 at 09:29:19PM -0000, [email protected] wrote: > Just tried out s3proxy - it's exactly what we're looking for. I tried setting > it up to use aws-v4 authorization against a filesystem backend like this: > > $ cat s3proxy.conf > s3proxy.authorization=aws-v4 > s3proxy.endpoint=http://0.0.0.0:8080 > s3proxy.identity=identity > s3proxy.credential=secret > jclouds.provider=filesystem > jclouds.filesystem.basedir=/tmp/s3proxy > > It seemed to work, but it can't find the container (test-bucket) when I do a > PUT that works against amazon. This came back from jclouds client when > configured to use the aws-s3 provider (I added an /etc/hosts entry for the > vhost-buckets issue - worked like a charm):
S3Proxy interpreted your PUT object operation as a PUT bucket operation; I suspect that you need to set s3proxy.virtual-host as documented here: https://github.com/gaul/s3proxy/blob/master/src/main/java/org/gaul/s3proxy/S3ProxyConstants.java#L50 If this does not help, could you follow up with a GitHub issue at https://github.com/gaul/s3proxy since this does not relate to the jclouds backend? -- Andrew Gaul http://gaul.org/
