-
Notifications
You must be signed in to change notification settings - Fork 177
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
Compatibility with latest aws s3 standards (signature v4) #107
Comments
I'm experiencing a similar issue:
services:
s3:
container_name: s3
image: "adobe/s3mock:2.1.0"
ports:
- "9090:9090"
- "9191:9191"
environment:
- initialBuckets=bucket import * as AWS from 'aws-sdk';
const s3Client = new AWS.S3({
endpoint: 'http://localhost:9090',
s3ForcePathStyle: true,
signatureVersion: 'v3',
});
s3Client.listObjects({ Bucket: 'bucket' }, (err, data) => {
console.log(err, data);
}); However, I get a different error.
When I don't specify
|
Let's track this as a issue to support V4 signing, and handle the pathStyleAccess=false support in a separate issue. |
I've created #144 for the bucket-subdomains support. |
Any update on signature v4 support ? |
The funny part is, that we’re using V4 signature by default already for a long long time, as I saw recently in the code. No one has looked into the actual problem at hand, though. A reproducible failing test case (in Java) would help a lot. |
This was in fact a bug, the same as described in #121. |
Spent a decent amount of time trying to get it work with official
[email protected]
library fornodejs
.Below I describe all problems I encountered and how I worked around them.
docker-compose.yml
and initializedmy-bucket
This error message was very confusing because the bucket was there and I could see it with
listBuckets
and I was able to upload to it with my postman query. What I found out later is that theaws-sdk
is using subdomain bucket naming convention whichadobe/s3mock
is not compatible with. I was able to fix it withs3ForcePathStyle: true
option on my s3 client configuration.After long investigation I found out that
adobe/s3-mock
is not compatible with latest version of aws signatures so I had to addsignatureVersion: 'v3'
to my s3 configuration.TLDR:
It's a great s3 mock server but is not compatible with the latest s3 standards
The text was updated successfully, but these errors were encountered: