AWS SDK v3 Compatibility

[devlsh]

AWS SDK v3 has been around for a little while now, and the benefits of using it (beyond being actively maintained) really outweigh the use of v2 for us.

Is there any chance of pushing this library forward using v3?

[michalkvasnicak]

@oyed sorry for late response. At the moment I don't have time for this but feel free to open a PR.

[fortena]

First of all I would like to thank you for this project, I have been using it for some time and it has really worked well!
Now I am however kind of getting stuck in a maintenance dilemma and I am not not sure what the best way forward is.
The problems are as following:
aws-sdk v2 is not included with node18 runtimes and adding it to a bundle is not going to be feasible either since how large it is.
Switching to a node18 runtime is nothing that needs happen right away but at some point in time this needs to happen.
We are also using the same approach as in the chat server example to run the project locally, but the plugins serverless-dynamodb-local and serverless-plugin-offline-dynamodb-stream are not getting any maintenance.
Unless they are replaced with something else I guess moving this project to aws-sdk v3 is blocked or up to individuals on figuring out a good way to run everything locally.

I guess I am querying a little bit on what the status of the project is. This is a very unique project that doesn't have any good alternatives that I know of. I am not sure how much I can contribute myself unfortunately but I am very much rooting for it to stay alive.

[pixelport]

I did a refactoring and created a pull request for this. If you already want to have a published version you can also use my fork: https://www.npmjs.com/package/@the_pixelport/aws-lambda-graphql