You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| +1473ms (node:51422) NOTE: The AWS SDK for JavaScript (v2) will enter maintenance mode
| +1473ms on September 8, 2024 and reach end-of-support on September 8, 2025.
This was closed as part of the move to the v2 repo but I'm reopening it since it still needs to be tracked. I'm not sure which part of SST v2 will break first (cdk change, aws-sdk support v2 fully removed, deprecated constructs, etc) but I wanted a ticket to add details to if this becomes a bigger issue.
I did a tiny bit of analysis and it appears that in the sst project itself aws-sdk (the v2 version) is only used in 4 places:
Original Ticket: sst/sst#3385
This was closed as part of the move to the v2 repo but I'm reopening it since it still needs to be tracked. I'm not sure which part of SST v2 will break first (cdk change, aws-sdk support v2 fully removed, deprecated constructs, etc) but I wanted a ticket to add details to if this becomes a bigger issue.
I did a tiny bit of analysis and it appears that in the
sst
project itselfaws-sdk
(the v2 version) is only used in 4 places:packages/sst/support/certificate-requestor/index.mjs
packages/sst/support/edge-function/edge-lambda-version.ts
packages/sst/support/edge-function/edge-lambda.ts
packages/sst/support/edge-function/s3-bucket.ts
Some of the examples are more involved than others but unless I'm missing something everything should be upgradable to v3 with some refactoring.
To clarify, I'm not actively working on a fix for this, it's not a problem yet but I think the changes are manageable if it does become an issue.
The text was updated successfully, but these errors were encountered: