Open thecherrytree opened 4 years ago
This might be a localstack issue? I've opened an issue with them as well: https://github.com/localstack/localstack/issues/1655
I had a similar issue. I use DynamodDB local which requires mock credentials - I set my .env to pass MOCK_ACCESS_KEY_ID and MOCK_SECRET_ACCESS_KEY respectively. After modifying calls to all dynamoDB and dynamoDBStreams such as:
new AWS.DynamoDBStreams({ region, accessKeyId: process.env.AWS_ACCESS_KEY_ID,
secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY });
Then it works fine. Perhaps these creds could be added to config?
Ahhh - the pleasure of having the same issue, searching for it and finding my own answer from last year as a solution. I should tip myself beer money.
Hi, thanks for building this. I'm hoping I can get it working.
My local setup is trying to call lambda from dynamodb stream. I'm using this in conjunction with serverless-offline and localstack.
However when I call list-streams, the stream is there:
awslocal dynamodbstreams list-streams
And when I describe-table:
awslocal dynamodb describe-table --table-name fte-dev
Here is my setup:
Serverless:
Not sure what I'm doing wrong here...