NodeJS AWS SDK The specified bucket does not exist (also weird `aws s3 ls` behavior)

Server is running via docker like:

docker run -e initialBuckets=bucket-1,bucket-2 -e root=/tmp/buckets -p 9090:9090 -p 9191:9191 -v /tmp/buckets:/tmp/buckets -t adobe/s3mock

(Version running is 2.1.18, which is latest as of this writing)

Im able to:

• Upload a Dockerfile
• Confirm I can download it again
• Confirm I can see the item listed with list-objects-v2

aws --endpoint-url http://localhost:9090 s3 cp Dockerfile s3://bucket-1/Dockerfile
aws --endpoint-url http://localhost:9090 s3 cp s3://bucket-1/Dockerfile ./s
aws --endpoint-url http://localhost:9090 s3api list-objects-v2 --bucket bucket-1

Heres where the bugs start:

• aws --endpoint-url http://localhost:9090 s3 ls bucket-1 isnt showing anything other than:

• NodeJS aws-sdk’s AWS.S3.putObject is always throwing “NoSuchBucket: The specified bucket does not exist” (with the server printing “Responding with status 404: The specified bucket does not exist.”)

• AWS.S3.listObjectsV2 isnt listing anything

My NodeJS S3 is configured like:

new aws.S3({
    accessKeyId: globals.AWS_ACCESS_KEY,
    secretAccessKey: globals.AWS_SECRET_KEY,
    endpoint: 'http://localhost:9090'
})

where the access and secret keys are just empty strings right now

My listObjectsV2 is:

const opts = {Bucket: 'bucket-1'}
const response = await s3.listObjectsV2(opts).promise()

My putObject is:

const obj = {
Bucket: 'bucket-1',
Body: 'some string',
Key: 'some-key'
}
await s3.putObject(obj).promise()

Let me know if I can provide any more info. Thanks!

[yonilerner]

After more digging, it seems like I may be able to force the desired behavior with s3ForcePathStyle: true in the S3 SDK config

[timoe]

thx for reporting, looks like a Bug.