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
We have pushed a breaking change that throws the following error during deployment.
Received response status [FAILED] from custom resource. Message returned: Error: Cannot
find module 'aws-sdk'
Require stack:
- /var/task/index.js
- /var/task/__entrypoint__.js
- /var/runtime/index.mjs
The reason is that we have upgraded Node runtime in Lambda to v18, which drops AWS SDK v2 as a runtime dependency and instead includes v3.
Blast radius
Anybody who wants to upgrade to v2.2.0 will have their stack deployments rollback due to the above error. The existing deployment will not be affected.
Solutions
To mitigate the issue we have to either:
Downgrade Node runtime to v16 from v18.
Move aws-sdk to production dependencies section so that Lambda code includes the library, and remove from externals. ✅
The longterm solution is to migrated AWS SDK to v3. We will publish an intermediary release to mitigate the issue, then will push a longterm solution.
The text was updated successfully, but these errors were encountered:
We have pushed a breaking change that throws the following error during deployment.
The reason is that we have upgraded Node runtime in Lambda to v18, which drops AWS SDK v2 as a runtime dependency and instead includes v3.
Blast radius
Anybody who wants to upgrade to v2.2.0 will have their stack deployments rollback due to the above error. The existing deployment will not be affected.
Solutions
To mitigate the issue we have to either:
aws-sdk
to productiondependencies
section so that Lambda code includes the library, and remove fromexternals
. ✅The longterm solution is to migrated AWS SDK to v3. We will publish an intermediary release to mitigate the issue, then will push a longterm solution.
The text was updated successfully, but these errors were encountered: