Cannot load credentials

Open
#10 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, javascript, node.js
Domain
cloud

Research direction

No source file, entry point, or test is identified. Reproduce the reported macOS setup using ~/.aws/credentials and inspect how the sample initializes the AWS SDK and loads credentials. Done means the sample can authenticate without the reported “Missing credentials in config” error.

Written by the indexing model from the issue text.

Description

I've created owner credentials on ~/.aws/credentials on my mac but it throw an error

[default]
aws_access_key_id = MY_ACCESS_KEY_ID
aws_secret_access_key = MY_SECRET_ACCESS_KEY

{ CredentialsError: Missing credentials in config
    at ClientRequest.<anonymous> (/Volumes/Data/Loint/aws-nodejs-sample/node_modules/aws-sdk/lib/http/node.js:83:34)
    at Object.onceWrapper (events.js:293:19)
    at emitNone (events.js:86:13)
    at ClientRequest.emit (events.js:188:7)
    at Socket.emitTimeout (_http_client.js:679:10)
    at Object.onceWrapper (events.js:293:19)
    at emitNone (events.js:86:13)
    at Socket.emit (events.js:188:7)
    at Socket._onTimeout (net.js:352:8)
    at ontimeout (timers.js:386:14)
  message: 'Missing credentials in config',
  code: 'CredentialsError',
  time: 2017-10-13T10:42:38.188Z,
  retryable: true,
  originalError: 
   { message: 'Could not load credentials from any providers',
     code: 'CredentialsError',
     time: 2017-10-13T10:42:38.188Z,
     retryable: true,
     originalError: 
      { message: 'Missing credentials in config',
        code: 'CredentialsError',
        time: 2017-10-13T10:42:38.178Z,
        retryable: true,
        originalError: [Object] } } }

please help

Dominant language
JavaScript
Stars
306
Forks
168
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/aws-nodejs-sample

All issues in aws-samples/aws-nodejs-sample

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.