-
Notifications
You must be signed in to change notification settings - Fork 305
unable to sync: Error: Non-file stream objects are not supported with SigV4 in AWS.S3 #175
Comments
Does anyone have a workaround for this issue? Either: |
Since my app was also using serverless I switched to using the serverless s3 client package and it works outside of |
This is solved by updating the |
Here's a workaround: Use the S3 Client from the latest SDK and pass it on to the const AWS = require('aws-sdk');
const s3 = require('s3');
const awsS3Client = new AWS.S3({
region: 'eu-central-1',
signatureVersion: 'v4'
});
const client = s3.createClient({
s3Client: awsS3Client
}); |
@LukasBombach still works 👍 Ran into the SigV4 issue using the |
Other folks stop just short of a full answer here but not including how to specify credentials in the AWS.S3 client, here's the full version that you'll need:
|
@LukasBombach Thank you sir, you've saved my day. |
@LukasBombach , @ryanostrom Here is the details : const awsS3Client = new AWS.S3({ const client = s3.createClient({
|
@manoj-compro me too |
@manoj-compro me too, same version of sdk and s3. |
@manoj-compro |
require('@auth0/s3') worked for me with same API |
Bro I did not understood , where i need to use this require('@auth0/s3') , can u share me the complete code . it will be helpfull |
uninstall S3 and install https://www.npmjs.com/package/@auth0/s3 this module as this is an extension of s3 and issue is fixed in @auth0/s3. All other functions/API are same. in Js file replace require('s3') by require('@auth0/s3') |
Thanks bro , Now there is no error thrown . now i am getting "done uploading" but the folder is not getting synced , or uploaded to S3 , here is my code . please check once . help me out this . const AWS = require('aws-sdk'); const awsS3Client = new AWS.S3( { const client = s3.createClient({
|
Nice work Bro |
@manoj-compro help me on the above code shared .. now i am getting error as "unable to sync: KMS.NotFoundException: Invalid arn" |
Below is the working code. if still not fix then try by changing region of bucket.
|
This solved the issue for us. |
Can you upgrade aws-sdk version?
The text was updated successfully, but these errors were encountered: