Invalid AWS Mock Access Key ID through a new AWS-SDK version

[henriklippke]

Due to a new AWS_SDK version only the following ACCESS KEY ID and SECRETS are allowed:

DynamoDB local version 2.0.0 and greater AWS_ACCESS_KEY_ID can contain the only letters (A–Z, a–z) and numbers (0–9).

Stackoverflow thread

[liam-ot]

@henriklippke hello, thanks for opening this PR

I was also having this issue and copied your solution into my local node_modules version of the serverless-dynamodb-local/index.js file which resolved the issue occurring on startup

however when i make graphQL calls the error still occurs but only with VTL templates

it seems there may be a deeper issue than just the key in the index.js file

EDIT: this is caused by the serverless-appsync-simulator package, i have opened this issue, and will (hopefully) open a PR soon

[domdomegg]

FYI: This package (serverless-dynamodb-local) doesn't appear to be maintained, with no new releases to NPM in over 2 years.

You can use serverless-dynamodb, a maintained fork, instead. (Disclaimer: I am a contributor to this fork). It is a drop-in replacement for this package, and is updated to fix this bug.

Migrating takes about 2 minutes, with a full guide in the README. Of course, it's all still open-source and MIT licensed. Ownership of this new package sits with a registered charity, that is committed to maintaining the package into the future and is open to contributions from the community.

[AshanFernando]

@henriklippke Thanks. I've merged the branch.

@domdomegg The problem is with the npm account thats being used to publish the packages. I will see whether we could get direct access via CI to publish new versions.

[yichenwang-myob]

@henriklippke Thanks. I've merged the branch.

@domdomegg The problem is with the npm account thats being used to publish the packages. I will see whether we could get direct access via CI to publish new versions.

Hi @AshanFernando , how is going with npm publish?