AWS Developer Tools Blog

Tag: aws-sdk-js-v3

Node.js logo

Why and how you should use AWS SDK for JavaScript (v3) on Node.js 18

The Node.js 18.x runtime was promoted to Active Long Term Support (LTS) on October 25th, 2022, and is now available in AWS Lambda. The AWS SDK for JavaScript (v3) is included by default in AWS Lambda Node.js 18 runtime as a convenience for developers building simpler functions. You can read about features in Node.js 18 […]

Node.js logo

Announcing the end of support for Node.js 12.x in the AWS SDK for JavaScript (v3)

This blog post is about AWS SDK for JavaScript (v3), and not AWS Lambda. As of Oct 2022, Lambda is planning Node.js 12.x deprecation on Mar 31, 2023. If your code uses Lambda Provided SDK, it’s v2 which continues to support Node.js 12.x Starting November 1, 2022, AWS SDK For JavaScript (v3) will no longer […]

Internet Explorer 11 logo

Announcing the end of support for Internet Explorer 11 in the AWS SDK for JavaScript (v3)

Starting October 1, 2022, AWS SDK For JavaScript (v3) will end support for Internet Explorer 11 (IE 11). The browser artifacts published in our npm packages will no longer target ES5. If your browser application depends on the AWS SDK for JavaScript (v3), we encourage you to support only modern secure and evergreen browsers like […]

Error Handling in Modular AWS SDK for JavaScript (v3)

In the version 3.53.0 of the modular AWS SDK for JavaScript (v3), we introduced concrete classes for AWS service exceptions which support asserting service exceptions with instanceof operator. In this post, we cover how to use it and how it improves the error handling experience. Why did we do it? Previously, the AWS SDK for […]

Screenshot of PackagePhobia showing install size reduction from 7.04 MB to 4.21 MB for STS Client of modular AWS SDK for JavaScript.

How we halved the publish size of modular AWS SDK for JavaScript clients

On December 15th, 2020, we announced the general availability of the AWS SDK for JavaScript, version 3 (v3). In v3, the modular packages reduce the bundle size of your application by ~75% as compared to that in AWS SDK for JavaScript, version 2 (v2). However, v3 had a large publish/install size for each modular package. In […]

Node.js logo

Announcing the end of support for Node.js 10.x in the AWS SDK for JavaScript (v3)

Starting January 1, 2022, AWS SDK For JavaScript (v3) will no longer support Node.js 10.x which was EOL on April 30, 2021. We encourage you to upgrade to Node.js 12.x or later. We recommend Node.js 14.x which was released on April 21, 2020 and became active LTS on October 27, 2020. Motivation As Node.js 10.x version […]

Mocking modular AWS SDK for JavaScript (v3) in Unit Tests

The AWS SDK for Javascript team would like to highlight the open-source community and it’s contributions. Today we welcome a guest blog written by Maciej Radzikowski on aws-sdk-client-mock, a library that allows easy mocking of AWS SDK for JavaScript (v3). On December 15th, 2020, AWS announced the general availability of the AWS SDK for JavaScript, version 3 […]

Indoor, Time, Waiting, Classic, Mood, White, Hourglass

Waiters in modular AWS SDK for JavaScript

On December 15th, 2020, we announced the general availability of the AWS SDK for JavaScript, version 3 (v3). In v3, the waiters are modular and not part of the client class. In this blog post, we cover the differences between waiters in v2 and v3, and how to use them. Background Waiters make it easier […]

signing image

Generate a presigned URL in modular AWS SDK for JavaScript

On December 15th, 2020, we announced the general availability of the AWS SDK for JavaScript, version 3 (v3). This blog shows you how to generate a presigned URL for an Amazon S3 bucket using the modular AWS SDK for JavaScript. Motivation A presigned URL gives you access to the object identified in the URL, provided […]

HTTP keep-alive is on by default in modular AWS SDK for JavaScript

On December 15th, 2020, we announced the general availability of the AWS SDK for JavaScript, version 3 (v3). In v3, we keep the Node.js HTTP connections alive by default. This blog post explains how it’s done. It also describes the benefits of keeping the sockets around, so they can be used for future requests without […]