aws-sign-v2

aws2
----

This signature is supported by (older) Amazon services, namely
ImportExport and
SimpleDB.
Fixed SimpleDB Select Signature Error
It also provides defaults for a number of core AWS headers and
request parameters, making it very easy to query AWS services, or
build out a fully-featured AWS library.

*NB: It is preferrable to use the newer, more secure
aws4 over this library for AWS services
that support AWS Signature Version 4.*

Example
-------

``javascript
var http = require('http'),
https = require('https'),
aws2 = require('aws2')

// given an options object you could pass to http.request
var opts = { host: 'sdb.amazonaws.com', path: '/?Action=ListDomains&Version=2009-04-15' }

// alternatively (as aws2 can infer the host):
opts = { service: 'sdb', path: '/?Action=ListDomains&Version=2009-04-15' }

aws2.sign(opts) // assumes AWS credentials are available in process.env

console.log(opts)
/*
{
host: 'importexport.amazonaws.com',
path: '/?Action=ListJobs&Timestamp=2013-01-12T01%3A25%3A55.553Z&SignatureVersion=2&SignatureMethod=...'
headers: { Host: 'importexport.amazonaws.com' }
}
*/

// we can now use this to query AWS using the standard node.js http API
http.request(opts, function(res) { res.pipe(process.stdout) }).end()
/*

...
*/
`

More options
------------

`javascript
// you can pass AWS credentials in explicitly (otherwise taken from process.env)
aws2.sign(opts, { accessKeyId: '', secretAccessKey: '' })

// create a utility function to pipe to stdout (with https this time)
function request(o) { https.request(o, function(res) { res.pipe(process.stdout) }).end(o.body || '') }

// aws2 can infer the HTTP method if a body is passed in
// method will be POST and Content-Type: 'application/x-www-form-urlencoded; charset=utf-8'
request(aws2.sign({ service: 'importexport', body: 'Action=ListJobs&Version=2010-06-01' }))
/*

...
*/

// can specify any custom option or header as per usual
request(aws2.sign({
service: 'importexport',
method: 'POST',
path: '/',
headers: {
'Content-Type': 'application/x-www-form-urlencoded'
},
body: 'Action=ListJobs&Version=2010-06-01'
}))
/*

...
*/
`

API
---



$3



This calculates and populates the Signature param of either
requestOptions.path or requestOptions.body depending on whether it is
a GET or POST request. Returns requestOptions as a convenience for
chaining.

requestOptions is an object holding the same options that the node.js
http.request
function takes.

The following properties of requestOptions are used in the signing or
populated if they don't already exist:

- hostname or host (will be determined from service and region if not given)
- method (will use 'GET' if not given or 'POST' if there is a body)
- path (will use '/' if not given)
- body (will use '' if not given)
- service (will be calculated from hostname or host if not given)
- region (will be calculated from hostname or host or use 'us-east-1' if not given)
- headers['Host'] (will use hostname or host or be calculated if not given)
- headers['Content-Type'] (will use 'application/x-www-form-urlencoded; charset=utf-8'
if not given and there is a body)
- headers['Date'] (used to calculate the signature date if given, otherwise new Date is used)

Your AWS credentials (which can be found in your
AWS console)
can be specified in one of two ways:

- As the second argument, like this:

`javascript
aws2.sign(requestOptions, {
secretAccessKey: "",
accessKeyId: ""
})
`

- From process.env, such as this:

`
export AWS_SECRET_ACCESS_KEY=""
export AWS_ACCESS_KEY_ID=""
export AWS_SESSION_TOKEN=""
`

(will also use AWS_ACCESS_KEY and AWS_SECRET_KEY if available)

The sessionToken property and AWS_SESSION_TOKEN environment variable are optional for signing
with IAM STS temporary credentials.

Installation
------------

With npm do:

`
npm install aws-sign-v2
``