npm install aws-sdk
|AWS.Request.client renamed to AWS.Request.service||
This is a backward incompatible change that is scoped to the
|Client and .client properties deprecated||
|New Amazon DynamoDB API version||
Version 0.9.8-pre.9 of the AWS SDK for Node.js includes a new Amazon DynamoDB API version
(2012-08-10) that contains backward-incompatible changes from the previous API
version (2011-12-05). By default, the SDK will load the latest available
API version when calling
In general, the API changes mostly affect the way you create and get items from a table, however other operations are also affected. For a more in-depth look at the new API, please see the Amazon DynamoDB API reference.
Creating a table changes from passing these parameters (with
Into the following:
Turns into this, where
Output from these requests will similarly drop
Locking into the 2011-12-05 API
If you want to continue using the Amazon DynamoDB 2011-12-05 API, you can lock your
API version in your global configuration with
This file can be loaded with:
|Removed Client Property||
Deprecated Client and .client properties. Also renames AWS.Request.client to AWS.Request.service to be consistent with the new service concept. This is a backward-incompatible change. Please see the "Upgrading Notes" at the top of this document for more information.
You can now create service objects with a
Note that only toplevel parameters can be bound. These parameters
will also be automatically ignored for operations that do not use
these parameters. For example, we can still use the
Added support for locking service objects to specific API versions through the
Note that the "dynamodb" value is the "service identifier" of the AWS.DynamoDB service object. Service identifiers can be found in the AWS SDK for Node.js API documentation.
You can also use the
Note that version constraint values are fuzzy, so it is possible to lock into a specific release date (globally and per-service) rather than an API version date. This ensures that you do not use any service API versions that are newer than the specified lock date. For instance, if you begin developing your project on 2013-04-18, you can lock into this version by specifying this date as your
Service documentation is also now updated to provide examples on constructing a service object with the appropriate version lock information for each available API version.
|IAM Roles for EC2||
Credentials will now be automatically loaded from an Amazon EC2 instance metadata service if IAM roles are configured on an Amazon EC2 instance. This allows for zero-configuration deployments.
Updated AWS.RDS to the latest API version (2013-02-12).
Added a new API version of the AWS.DynamoDB service. By default, creating a AWS.DynamoDB object will use this API.
Note that this API is not compatible with the previous version. For more information, see the "Upgrading Notes" at the top of this document.
Added proxy support to the SDK. To set a global proxy, configure the proxy
endpoint in the
Sample usage: Setting a custom timeout value of 500ms on Amazon S3 operations:
Creating a custom connection pool for a specific client over HTTP:
Note that increasing the connection pool size over HTTPS connections increases overhead for short-running processes.
The SDK will now follow all 3xx redirects with no delay. This change also
Credentials can now be loaded asynchronously through the
Added AWS.MetadataService client to query Amazon EC2 instance metadata. To make a request, call:
|Parameter Validation / Serialization|
Propagate errors from all callbacks up to main runloop (GitHub issue #74).
Fixed an issue where credentials were being ignored when initialized via service or client objects. (GitHub issue #72)
Supported API Versions
This release of the SDK supports the following API versions:
|Amazon Elastic Compute Cloud||2013-02-01|
|Amazon Elastic MapReduce||2009-03-31|
|Amazon Elastic Transcoder||2012-09-25|
|Amazon Relational Database Service (Beta)||2013-02-12|
|Amazon Route 53||2012-12-12|
|Amazon Simple Email Service||2010-12-01|
|Amazon Simple Notification Service||2010-03-31|
|Amazon Simple Queue Service||2012-11-05|
|Amazon Simple Storage Service||2006-03-01|
|Amazon Simple Workflow Service||2012-01-25|
|AWS Data Pipeline||2012-10-29|
|AWS Direct Connect||2012-10-25|
|AWS Elastic Beanstalk||2010-12-01|
|AWS Identity and Access Management||2010-05-08|
|AWS Security Token Service||2011-06-15|
|AWS Storage Gateway||2012-06-30|
|Elastic Load Balancing||2012-06-01|