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
Copy file name to clipboardExpand all lines: README.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,13 +195,13 @@ we have them listed in [UPGRADING.md](https://github.com/aws/aws-sdk-js-v3/blob/
195
195
196
196
### General Info
197
197
198
-
The Lambda provided AWS SDK is set to a specific minor version, and NOT the latest version. To
199
-
determine which version of the SDK is included with the runtime you're using,
200
-
see [Runtime-included SDK versions](https://docs.aws.amazon.com/lambda/latest/dg/lambda-nodejs.html#nodejs-sdk-included)
201
-
in the Lambda Developer Guide. To maintain full control of your dependencies, and to maximize
202
-
backward compatibility during automatic runtime updates, we recommend that you always include
203
-
the SDK modules your code uses in your function's deployment package or in a Lambda layer.
204
-
See [Backward compatibility](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-update.html#runtime-update-compatibility)
198
+
The Lambda provided AWS SDK is set to a specific minor version, and NOT the latest version. To
199
+
determine which version of the SDK is included with the runtime you're using,
200
+
see [Runtime-included SDK versions](https://docs.aws.amazon.com/lambda/latest/dg/lambda-nodejs.html#nodejs-sdk-included)
201
+
in the Lambda Developer Guide. To maintain full control of your dependencies, and to maximize
202
+
backward compatibility during automatic runtime updates, we recommend that you always include
203
+
the SDK modules your code uses in your function's deployment package or in a Lambda layer.
204
+
See [Backward compatibility](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-update.html#runtime-update-compatibility)
205
205
to learn more.
206
206
207
207
The performance of the AWS SDK for JavaScript v3 on node 18 has improved from v2 as seen in the [performance benchmarking](https://aws.amazon.com/blogs/developer/reduce-lambda-cold-start-times-migrate-to-aws-sdk-for-javascript-v3/)
@@ -702,6 +702,8 @@ Note that you can also use the native JavaScript implementation of SigV4a that d
702
702
703
703
### Using JavaScript (non-CRT) implementation of SigV4a
704
704
705
+
Note: Use of AWS SignatureV4a in the browser (JS implementation) is not recommended, due to the bundle size of the SigV4a signing algorithm code. Consider whether there are other ways to achieve your desired application functionality without the use of sigv4a before installing these packages.
706
+
705
707
AWS SDK for JavaScript v3 now supports a native JavaScript version of SigV4a that can be used in browsers and Node, and does not depend on [AWS Common Runtime (CRT)](https://docs.aws.amazon.com/sdkref/latest/guide/common-runtime.html). This is an alternative to the AWS CRT version, so you don't need to have both packages together.
706
708
707
709
If neither the CRT components nor the JavaScript SigV4a implementation are installed, you will receive an error like:
0 commit comments