Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Clarify AWS credentials requirements for local DB

See original GitHub issue

It seems that the setupdb plugin needs the [default] profile in ~/.aws/credentials to have the same aws_access_key_id and aws_secret_access_key as the profile in admin.dev.

I tried setting AWS_DEFAULT_PROFILE to the profile in admin.dev, but didn’t work.

Is this a bug?

Here the error I get:

mutation createUserTest { createUser ....

"errors": [
    {
      "message": "Missing credentials in config",
      "originalError": {
        "cause": {
          "message": "Missing credentials in config",
          "code": "CredentialsError",
          "time": "2016-05-04T14:37:16.127Z",
          "originalError": {
            "message": "Could not load credentials from any providers",
            "code": "CredentialsError",
            "time": "2016-05-04T14:37:16.127Z",
            "originalError": {
              "message": "Connection timed out after 1000ms",
              "code": "TimeoutError",
              "time": "2016-05-04T14:37:16.127Z"
            }
          }
        },
        "isOperational": true,
        "code": "CredentialsError",
        "time": "2016-05-04T14:37:16.127Z",
        "originalError": {
          "message": "Could not load credentials from any providers",
          "code": "CredentialsError",
          "time": "2016-05-04T14:37:16.127Z",
          "originalError": {
            "message": "Connection timed out after 1000ms",
            "code": "TimeoutError",
            "time": "2016-05-04T14:37:16.127Z"
          }
        }
      }
    }
  ]

Issue Analytics

State:
Created 7 years ago
Reactions:4
Comments:28 (11 by maintainers)

Top GitHub Comments

9reactions

TomBartacommented, May 17, 2016

I had this problem today, too.

export AWS_ACCESS_KEY_ID=id_key export AWS_SECRET_ACCESS_KEY=access_key

solved it on my OSX and Ubuntu 16.04 machines.

1reaction

laardeecommented, May 17, 2016

@ismarslomic yes, I had the aws cli installed beforehand and I probably used similar instructions when I configured the credentials. I have exactly same versions of python, serverless and os x installed.