Local DynamoDB doesn't work.

[Qard]

I'm trying to configure the DynamoDB client to connect to a local dynamodb for dev like this:

var db = new AWS.DynamoDB({
  endpoint: new AWS.Endpoint(url)
});

It throws this config error here:

aws-sdk-js/lib/event_listeners.js

Line 82 in 07e0bb8

{code: 'ConfigError', message: 'Missing region in config'});

Setting region doesn't make sense when connecting to local dynamodb, but If I put it in anyway, it then fails on:

aws-sdk-js/lib/event_listeners.js

Line 73 in 07e0bb8

{code: 'CredentialsError', message: 'Missing credentials in config'});

[chrisradek]

@Qard
You also need to specify credentials. Since you're working with your local dynamodb, I don't believe your credentials have to be valid, but the SDK needs something otherwise it will continue to display the Missing credentials in config error.

Let me know if that helps or if you need an example!

[Qard]

Yeah, I figured that much out. It seems broken to me that I'd have to set a bunch of configs that it doesn't actually use to get it to work properly though.

[jeskew]

@Qard Your credentials are used by DynamoDB local to maintain separate databases for different users. Your credentials won't be checked, but those configuration parameters do serve a purpose.

[Qard]

Not according to the docs on local dynamodb. http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tools.DynamoDBLocal.html#Tools.DynamoDBLocal.Differences

[jeskew]

If you scroll up on the page you've linked to, you'll see documentation on the --sharedDb option. If not set, your database will be saved in a file named {myaccesskeyid}_{region}.db.

I'll let the doc author know that "Regions and distinct AWS accounts are not supported at the client level" is confusingly worded.

[Alex0007]

Getting same error
UnrecognizedClientException: The security token included in the request is invalid. when trying to create tables in local db

when i provided valid credentials, table created, but on aws service, not local

This functionality become broken on npm 2.2.32 version

@chrisradek

[chrisradek]

@Alex0007
Can you provide a code snippet? Are you updating the endpoint to look at your local database?

[Alex0007]

@chrisradek
I'm using vogels (vogels.AWS is AWS) and after updating aws-sdk i'm getting error there

import vogels from 'vogels'
import requireDir from 'require-dir'

vogels.AWS.config.update({
  endpoint: process.env.AWS_DYNAMODB_ENDPOINT,
  accessKeyId: process.env.AWS_ACCESS_KEY_ID,
  secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
  region: process.env.AWS_REGION
})

module.exports = async function() { // create tables

  return new Promise(function (resolve, reject) {
    requireDir()

    vogels.createTables((err) => {
      if (err) {
        console.log(`Error creating tables: ${err}`)
        return reject(`Error creating tables: ${err}`)
      }
      resolve()
    })
  })

}

[Alex0007]

@chrisradek @jeskew
Please, reopen this issue, because the problem really exist

[jeskew]

@Alex0007 I'm unable to reproduce the behavior you're experiencing. Have you verified that process.env.AWS_DYNAMODB_ENDPOINT is properly set?

[Alex0007]

@jeskew
it seems that code working again on aws-sdk latest version

[jeskew]

Glad to hear everything worked out. Let me know if you have any further questions.

[ilanle]

Getting the same error now.
Just npmd the latest release a few minutes ago,
I get this from dynamo
UnrecognizedClientException: The security token included in the request is invalid

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.