-
Notifications
You must be signed in to change notification settings - Fork 6
s3param doesn't seem to be send along with server-initiated file uploads #21
Comments
same issue here |
const options =
the file uploaded but permission and StorageClass are wrong |
Not sure if it's the same issue, but I'm trying to pass the signature_version thought the s3config parameter and also it's failing... const options =
and the error InvalidRequest
The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
21F128804941FB24
wp4cFOh2aNdfWAFpljs6CkJNi24hkWOfUDkWqEb4QEE6tSwrzBqSU8Iq9b9NAuD2UuQhG0/KiME=
|
any idea here? still same problem :( |
You should put all params in
|
const options =
{
key: 'XX'
, secret: 'YY'
, bucket: 'stacktapimages'
, region: 'eu-central-1'
// Let's use the custom s3params to upload this file as publicly readable by anyone
, s3params:
{
ContentType: 'image/jpeg',
ACL: 'public-read'
}
}
sails.s3 = require('skipper-better-s3')(options);
The file does upload to S3, but if I check the uploaded file it doesn't have the correct mime type nor does it have the permission for everyone to open/download.
the following is the part that uploads to the file to s3:
const receiver = sails.s3.receive()
receiver.write(file, () => {
The text was updated successfully, but these errors were encountered: