Open arpadgabor opened 10 months ago
Ahhh I missed that. I think just moving aws-sdk v1 from dev dep to dep would be quick fix. I know that aws sdk v1 is now deprecated but repairing handler to work is much important than refactoring code to use aws sdk v2 IMO.
So my plan would be like:
It would be so appreiciated if you can submit for 1 for now :)
Created a PR for bundling: #85
As you are probably aware, AWS SDK v2 is not included in the latest Node runtimes. From what I see, the lambda code is still using the v2 version instead of v3, and the custom resource fails to run with the following error:
As there currently is no way to deploy the construct in the current state, I think a short-term fix would be to provide a 2.1.1 release with Node 16 runtime (as it's still supported until June). A longer-term and simple option would be to bundle the v2 SDK. Finally, the harder option would be a complete upgrade.
I'll see if I can get a PR started for the upgrade.