AWS Developer Tools Blog

Introducing the AWS SDK for JavaScript Blog

Introducing the AWS SDK for JavaScript Blog

Today we’re announcing a new blog for the AWS SDK for JavaScript. On this blog, we will be sharing the latest tips, tricks, and best practices when using the SDK. We will also keep you up to date on new developments in the SDK and share information on upcoming features. Ultimately, this blog is a place for us to reach out and get feedback from you, our developers, in order to make our SDK even better.

We’re excited to finally start writing about the work we’ve done and will be doing in the future; there’s a lot of content to share. In the meantime, here’s a little primer on the AWS SDK for JavaScript, if you haven’t had the chance to kick its tires.

Works in Node.js and Modern Browsers

The SDK is designed to work seamlessly across Node.js and browser environments. With the exception of a few environment-specific integration points (like streams and file access in Node.js, and Blob support in the browser), we attempt to make all SDK API calls work the same way across all of your different applications. One of my favorite features is the ability to take snippets of SDK code and move them from Node.js to the browser and back with at most a few changes in code.

In Node.js you can install the SDK as the aws-sdk npm package:

$ npm install aws-sdk --save

In the browser, you can use a hosted script tag to install the SDK or build your own version. More details on this can be found in our guide.

Full Service Coverage

The SDK has support for all the AWS services you want to use, and we keep it up to date with new API updates as they are released. Note that although some services in the browser require CORS to work over the web, we are continually working to expand the list of CORS-supported services. You can also take advantage of JavaScript in various local environments (Chrome and Firefox extensions, iOS, Android, WinRT and other mobile applications), which do not enforce CORS and develop your AWS-backed applications there; and you can do that with a custom build of the SDK today.

Open Source

Finally, the thing about the SDK that excites me the most is the fact that the entire SDK is openly developed and shared on GitHub. Feel free to check out the SDK code, post issue reports, and even submit pull requests with fixes or new features. Our SDK depends on feedback from our developers, so we love to get reports and pull requests. Send away!

More to Come

We will be posting much more information about the SDK on this blog. We have plenty of exciting things to share with you about new features and improvements to the library. Bookmark this blog and check back soon as we publish more information!