Mikael Finstad

I think it needs to rewritten to use aws-sdk-v3 instead, like I just did with cognito-backup: https://github.com/mifi/cognito-backup/commit/431e70723a95ecf29d67634f52f5ec2eacfef41e

I think the AWS SDK (which we use) already retries when it gets this error. Maybe it gave up retrying? See https://stackoverflow.com/questions/31468379/how-to-solve-throughput-error-for-dynamodb

I think it needs to rewritten to use aws-sdk-v3 instead, like I just did with cognito-backup: https://github.com/mifi/cognito-backup/commit/431e70723a95ecf29d67634f52f5ec2eacfef41e

Try newest version now.

Could you show exactly where the key is located in the JSON? is it `index.ProvisionedThroughput.LastDecreaseDateTime` or `index.LastDecreaseDateTime`? im also happy to accept a pr to fix this

Hi! thanks for the PR Am I right that there are four changes you want? 1. Set custom endpoint 2. Delete existing table before import 3. Supporting some table types...

Hi again. I just did a rewrite to ESM. If someone wants to address my concerns above and create separate PR's I'm happy to merge

Yes, PR welcome

unfortunately not, but it should be possible to implement some onProgress function

Oww. That's a weird one. could you try node 16 and see if it helps? and possibly ffmpeg 4.3.x