One reason you might encounter this behaviour is using non-maintained packages, which still use the older behaviour internally. This is discussed in https://github.com/99x/serverless-dynamodb-local/pull/298
To fix this, upgrade the packages to maintained forks (disclaimer: I am a contributor to these forks), for example:
Would the concepts mentioned in this article apply to the following issue?
- EXPERTpublished 2 months ago
- EXPERTpublished 4 months ago
- asked 8 months ago
- How can I troubleshoot an EC2 Windows instance that is unreachable or can't reach the DNS after upgrading the drivers?AWS OFFICIALUpdated a year ago
- How can I resolve the AWS KMS key policy error "Policy contains a statement with one or more invalid principals"?AWS OFFICIALUpdated 3 months ago