AWS Missing credentials when I try send something to my S3 Bucket (Node.js)

Question

I'm having this issue since yesterday, and I'm having trouble for find a solution.

I'm trying to send somethings to my S3 bucket, but this message appear in my console when I try:

{ [CredentialsError: Missing credentials in config]
  message: 'Missing credentials in config',
  code: 'CredentialsError',
  errno: 'Unknown system errno 64',
  syscall: 'connect',
  time: Thu Oct 09 2014 14:03:56 GMT-0300 (BRT),
  originalError: 
   { message: 'Could not load credentials from any providers',
     code: 'CredentialsError',
     errno: 'Unknown system errno 64',
     syscall: 'connect',
     time: Thu Oct 09 2014 14:03:56 GMT-0300 (BRT),
     originalError: 
      { code: 'Unknown system errno 64',
        errno: 'Unknown system errno 64',
        syscall: 'connect',
        message: 'connect Unknown system errno 64' } } }

And this is my code:

var s3 = new AWS.S3();
AWS.config.loadFromPath('./AwsConfig.json'); 

    s3.putObject(params, function(err) {
        if(err) {
            console.log(err);
        }
        else {
            console.log("Succes");
        }
});

The credentials are correct. Does anyone know what can be? I've searching but I not find anywhere the solution.

My credentials(fake):

{
    "accessKeyId": "BLALBLALBLALLBLALB",
    "secretAccessKey": "BLABLALBLALBLALBLLALBLALLBLALB",
    "region": "sa-east-1",
    "apiVersions": {
      "s3": "2006-03-01",
      "ses": "2010-12-01"
    }
}

EDIT:

For help, all the code:

var fs = require('fs');
var AWS = require('aws-sdk');


var s3 = new AWS.S3();
AWS.config.loadFromPath('./MYPATH.json'); //this is my path to the aws credentials.


var params = {
        Bucket: 'testing-dev-2222',
        Key: file,
        Body: fs.createReadStream(file)
    };

s3.putObject(params, function(err) {
    if(err) {
        console.log(err);
    }
    else {
        console.log("Success");
    }
});

New err:

Error uploading data:  { [PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.]
  message: 'The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.',
  code: 'PermanentRedirect',
  time: Thu Oct 09 2014 14:50:02 GMT-0300 (BRT),
  statusCode: 301,
  retryable: false }

can you add your config.json file (hide the real credentials)? — xShirase
– xShirase, Commented Oct 9, 2014 at 17:12
One interesting thing, I'm using sns to send me an email when things are sent to my bucket (my backup). He is sending me the same error. How he can access the sns if the credentials are wrong? — user3998237
– user3998237, Commented Oct 9, 2014 at 17:16
may i know ,what comes in 'file'?(Key: file)..whether 'tmp/filename' or our defined filepath?Is it possible to directly upload our files to aws s3 instead getting uploaded initially to our tmp folder and getting transferred to aws s3??? — Jagadeesh
– Jagadeesh, Commented Jun 27, 2017 at 9:39

DesignMonkeyJim · Accepted Answer · 2023-03-11 16:14:49Z

83

Try hardcoding your params and see if you get the error again :

AWS.config.update({
    accessKeyId: "YOURKEY",
    secretAccessKey: "YOURSECRET"
}); 

//for simplicity. In prod, use loadConfigFromFile, or env variables, or if logged in using 

var s3 = new AWS.S3({ region: "sa-east-1" }); //region can be set in here

var params = {
    Bucket: 'makersquest',
    Key: 'mykey.txt',
    Body: "HelloWorld"
};

s3.putObject(params, function (err, res) {
    if (err) {
        console.log("Error uploading data: ", err);
    } else {
        console.log("Successfully uploaded data to myBucket/myKey");
    }
});

Good resource here

edited Mar 11, 2023 at 16:14

DesignMonkeyJim

1,9451 gold badge14 silver badges23 bronze badges

answered Oct 9, 2014 at 17:19

xShirase

12.4k4 gold badges55 silver badges86 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

mylord Over a year ago

I still get this error using the correct keys. Any other ideas?

trainoasis Over a year ago

For me it says XMLHttpRequest cannot load mybucketnamehere.s3.amazonaws.com/mykey.txt. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'mypage_on_localhost' is therefore not allowed access. The response had HTTP status code 403. I set CORS to allow this domain. Any ideas?

Aanchal1103 Over a year ago

The link is broken.

Oswaldo Zapata Over a year ago

I had this same issue, i resolved this using my accesskey and secret access key like described here. thanks a lot.

Mahesh Gaikwad Over a year ago

@xShirase Awesome man. Was facing issue for 3 hours. This helped me a lot. Thank you very much :)

|

Hugh McKee · Accepted Answer · 2015-10-16 16:36:02Z

62

I had the same problem until I reversed the two lines:

var s3 = new AWS.S3();
AWS.config.loadFromPath('./AwsConfig.json');

to this:

AWS.config.loadFromPath('./AwsConfig.json'); 
var s3 = new AWS.S3();

answered Oct 16, 2015 at 16:36

Hugh McKee

6215 silver badges2 bronze badges

5 Comments

loretoparisi Over a year ago

This is right the solution, that avoid to hardcode credentials.

user659025 Over a year ago

I'm trying to upload files to S3. After doing this switch and removing the region in my config, as stated in the currently marked answer, uploading worked. Thanks @Hugh McKee!

Samuel Duzett Over a year ago

It seems insane that this is the solution, but it did it for me

Quinn Keaveney Over a year ago

Why does this work? ...because the credentials aren't loaded before you create the variable.

Sam Luther Over a year ago

this drove me insane for quite a while

Dipankar Biswas · Accepted Answer · 2016-08-29 00:23:39Z

12

I was having the same error. But I found the issue. I was using wrong Environment variable name. From NodeJS to S3, I need to use the following variable names:

process.env.AWS_ACCESS_KEY_ID = 'XXXXXXXXXXXXXXXXXXX';
process.env.AWS_SECRET_ACCESS_KEY = 'XXXXXXXXXXXXXXXXXXXXXXXXXX';
process.env.AWS_REGION = 'us-east-1';

Once I corrected the variable names, it just ran fine. regards, Dipankar

answered Aug 29, 2016 at 0:23

Dipankar Biswas

1411 silver badge3 bronze badges

1 Comment

Ramachandran Mani Over a year ago

Thanks. This worked for me. Any idea why this env variable name matters ? Ideally, we should be specifying any env variable name and while doing aws update only json key should matter.

Tim Siwula · Accepted Answer · 2017-01-21 20:20:58Z

12

Try changing the user in my aws config file from a specific user to [default].

$nano .aws/credentials

[default]
aws_access_key_id = xyz
aws_secret_access_key = xyz

If you do not have this file, create it and get your keys or generate new one from aws iam user keys.

answered Jan 21, 2017 at 20:20

Tim Siwula

95111 silver badges16 bronze badges

Comments

Gopal Shukla · Accepted Answer · 2015-06-28 11:44:27Z

0

I tried above option and even that did not work, so I created new config object and this below code worked

 AWS.config = new AWS.Config();
 AWS.config.accessKeyId = "AccessKey";
 AWS.config.secretAccessKey = "SecretAccessKey";

answered Jun 28, 2015 at 11:44

Gopal Shukla

1671 gold badge3 silver badges10 bronze badges

2 Comments

Randy L Over a year ago

sort of defeats the purpose though

loretoparisi Over a year ago

It works, bad it is a bad idea to hardcode credentials, consider that the aws-sdk will look at environment variables as well, otherwise use a file.

Dustin Graves · Accepted Answer · 2016-06-14 20:42:19Z

0

I had a similar issue when trying to load the config file from anywhere other than the root directory.

I was able to load the json file natively in node, then just pass the object that was parsed to AWS.config.update()

import AWS from 'aws-sdk'
import config from '../aws.json' 
AWS.config.update(config);

answered Jun 14, 2016 at 20:42

Dustin Graves

12 bronze badges

Comments

Sudarshan kumar · Accepted Answer · 2018-12-13 04:44:16Z

0

This resolved my issue .

Used the sample code from the Cognito Console and added it to the of the document.
Enabled Unauthenticated access on the identity pool.

Most important

Fixed the Trust Relationship policy in the unauth role so the Cognito Service could assume the role.
Do not hard code credential in the file .

answered Dec 13, 2018 at 4:44

Sudarshan kumar

1,5895 gold badges43 silver badges91 bronze badges

Collectives™ on Stack Overflow

AWS Missing credentials when I try send something to my S3 Bucket (Node.js)

7 Answers 7

7 Comments

5 Comments

1 Comment

Comments

2 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

7 Comments

5 Comments

1 Comment

Comments

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related