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
Currently, the module @aws-crypto/kms-keyring-node uses the AWS SDK as a dependency and that makes the bundle package big for AWS Lambdas, I think this SDK should cover AWS Lambda scenarios as well.
Solution:
The aws-sdk dependency should be moved to peerDependencies in the package.json, making it possible for the clients to choose to use the AWS SDK as devDependency or explicit dependency.
Major Version 4.0.0 of the AWS ESDK for JS has been released. This major version should address the problems you outline on this issue. Please let us know if you have any questions.
AWS Crypto Tools
Problem:
Currently, the module
@aws-crypto/kms-keyring-node
uses the AWS SDK as a dependency and that makes the bundle package big for AWS Lambdas, I think this SDK should cover AWS Lambda scenarios as well.Solution:
The
aws-sdk
dependency should be moved topeerDependencies
in thepackage.json
, making it possible for the clients to choose to use the AWS SDK as devDependency or explicit dependency.Related issue
The text was updated successfully, but these errors were encountered: