NodeJS modules for talking to IaaS providers, such as Amazon AWS, RackspaceCloud, OpenStack!
_______ _______ _______ _______
( ___ )|\ /|( ____ \( ____ \|\ /|( )
| ( ) || ) ( || ( \/| ( \/| ) ( || () () |
| (___) || | _ | || (_____ | (_____ | | | || || || |
| ___ || |( )| |(_____ )(_____ )| | | || |(_)| |
| ( ) || || || | ) | ) || | | || | | |
| ) ( || () () |/\____) |/\____) || (___) || ) ( |
|/ \|(_______)\_______)\_______)(_______)|/ \|
NodeJS client libraries for talking to lots of Web Service APIs.
IRC : Come and say hello in #awssum on Freenode. :)
Btw: AwsSum is being used at Medium.com! Yay!
AwsSum now has a new docs site. This README.md will eventually disappear in favour of that site.
$ npm -d install awssum
var awssum = require('awssum');
var amazon = awssum.load('amazon/amazon');
var S3 = awssum.load('amazon/s3').S3;
var s3 = new S3({
'accessKeyId' : accessKeyId,
'secretAccessKey' : secretAccessKey,
'region' : amazon.US_EAST_1
});
s3.ListBuckets(function(err, data) {
if (err) {
// something went wrong with the request
console.log(err);
return;
}
// request was fine
console.log(data);
});
s3.CreateBucket({ BucketName : 'my-bucket' }, function(err, data) {
if (err) {
console.log(err);
return;
}
// creation of bucket was ok, now let's put an object into it
s3.PutObject({
BucketName : 'my-bucket',
ObjectName : 'some.txt',
ContentLength : '14',
Body : "Hello, World!\n",
}, function(err, data) {
console.log(err)
console.log(data)
});
});
Currently AwsSum has coverage of the following services:
<tr>
<td>Twitter</td>
<td>Twitter</td>
<td>OAuth 1.0a</td>
<td>✔</td>
<td>98/101</td>
</tr>
<tr>
<td>Tumblr</td>
<td>Tumblr</td>
<td>OAuth 1.0a</td>
<td>✔</td>
<td>0/???</td>
</tr>
<tr>
<td>Xero</td>
<td>Xero</td>
<td>OAuth 1.0a</td>
<td>✔</td>
<td>~12/~40?</td>
</tr>
<tr>
<td>Yahoo!</td>
<td>Contacts</td>
<td>OAuth 1.0a</td>
<td>✔</td>
<td>3/???</td>
</tr>
| Company | Service | SignatureMethod | Signature | Operations |
|---|---|---|---|---|
| Amazon | SimpleDB | Signature v2, (HmacSHA256) | ✔ | 10/10 (100%) |
| SQS | Signature v2, (HmacSHA256) | ✔ | 15/15 (100%) | |
| SES | X-Amzn-Authorization "AWS3-HTTPS" header, (HmacSHA256) | ✔ | 18/18 (100%) | |
| SNS | Signature v2, (HmacSHA256) | ✔ | 15/15 (100%) | |
| S3 | Authorization "AWS" header (SHA1) | ✔ | 43/43 (100%) | |
| EC2 | Signature v2, (HmacSHA256) | ✔ | 134/134 (100%) | |
| Route53 | X-Amzn-Authorization "AWS3-HTTPS" header, (HmacSHA256) | ✔ | 7/7 (100%) | |
| ElastiCache | Signature v2, (HmacSHA256) | ✔ | 21/21 (100%) | |
| CloudFront | Authorization "AWS" header (sha1) | ✔ | 21/21 (100%) | |
| Elastic Load Balancing (ELB) | Signature v2, (HmacSHA256) | ✔ | 23/23 (100%) | |
| DynamoDB | Signature v4, (Hmac256) | ✔ | 13/13 (100%) | |
| Simple Workflow Service | X-Amzn-Authorization "AWS3" (HmacSHA256) | ✔ | 31/31 (100%) | |
| Flexible Payments Service (FPS) | Signature v2, (HmacSHA256) | ✔ | 22/22 (100%) | |
| CloudWatch | Signature v2, (HmacSHA256) | ✔ | 11/11 (100%) | |
| Identity and Access Management (IAM) | Signature v4, (Hmac256) | ✔ | 69/69 (100%) | |
| Relational Database Service (RDS) | Signature v2, (HmacSHA256) | ✔ | 39/39 (100%) | |
| CloudFormation | Signature v2, (HmacSHA256) | ✔ | 12/12 (100%) | |
| Instance MetaData (IMD) | [none] | ✔ | 2/2 (100%) | |
| ElasticBeanstalk | Signature v2, (Hmac256) | ✔ | 29/29 (100%) | |
| AutoScaling | Signature v2, (Hmac256) | ✔ | 33/33 (100%) | |
| Import/Export | Signature v2, (Hmac256) | ✔ | 5/5 (100%) | |
| Elastic MapReduce (EMR) | Signature v2, (Hmac256) | ✔ | 7/7 (100%) | |
| Storage Gateway | Signature v4, (Hmac256) | ✔ | 26/26 (100%) | |
| CloudSearch (CS) | Signature v4, (Hmac256) | ✔ | 20/20 (100%) | |
| Glacier | Signature v4, (Hmac256) | ✔ | 19/19 (100%) |
In future releases we will be targeting (in no particular order):
There are lots of services out there, so please Request or Sponsor Development if you'd like one implemented.
node-awssum is an abstraction layer to many web service APIs. It abstracts out the service endpoints, the HTTP verbs to use, what headers and parameters to set, how to sign the request and finally how to decode the result. It let's you pass a data structure in and get a data structure out. It also helps in the odd small way when dealing with complex input such as creating XML (e.g. Amazon S3), JSON data structures (e.g. Amazon SQS) or parameters with lots of values (e.g. Amazon SimpleDB).
In saying this, there are some web service operations that are inherently nasty and since node-awssum is essentially a proxy to the operation itself it can't abstract away all nastiness.
For an example of where node-awssum helps is when creating a Bucket in Amazon S3. We take a single 'LocationConstraint' parameter in the 'createBucket' call and node-awssum takes that and builds (the horrible) XML which it needs to send with the request. This makes it much easier to perform calls to the various web services and their individual operations since this simple notion is across all web services.
However, there are also examples of where node-awssum can't really help make the operation nicer. Many of the Amazon Web Services return XML which we blindly convert to a data structure and return that to the caller. In these cases we don't perform any kind of manipulation or conversion to a canonical structure to make the returned data nicer. In these cases, a small library which sits on top of node-awssums libraries may be a good choice (see winston-simpledb for an example of this - http://github.com/appsattic/winston-simpledb). This would be especially true for SimpleDB where the higher level library could perform number padding, date conversions, creation of multi-field indexes and default field values - none of which node-awssum does.
Example 1. This is what node-awssum looks like when adding a topic to Amazon's Simple Notification Service:
sns.CreateTopic({ TopicName : 'my-topic' })
=> {
Headers: {
date: 'Wed, 16 May 2012 10:32:24 GMT',
content-type: 'text/xml',
x-amzn-requestid: '6d099dcd-9f42-11e1-a8a2-0f9b48899c6b',
content-length: '315'
},
Body: {
CreateTopicResponse: {
@: {
xmlns: 'http://sns.amazonaws.com/doc/2010-03-31/'
},
ResponseMetadata: {
RequestId: '6d099dcd-9f42-11e1-a8a2-0f9b48899c6b'
},
CreateTopicResult: {
TopicArn: 'arn:aws:sns:us-east-1:616781752028:my-topic'
}
}
},
StatusCode: 200
}
What you would probably like to do is the following (with an example SNS Wrapper Library):
snsWrapperLibrary.createTopic('my-topic')
=> arn:aws:sns:us-east-1:616781752028:my-topic
This is pretty easy to do but annoying to have to find and extract the information you really want. node-awssum comes with some example libraries. :)
Example 2. Saving some attributes for AWS SimpleDB.
...
This library has a number of uses but mostly it should be used from within a more friendly wrapper library. Let's look at some examples.
Example 1: A SimpleDB Wrapper library. Since node-awssum doesn't do any kind of conversion of the values you want to put into SimpleDB, it would make sense that you used a library which did those conversions for you, such as padding integer values, normalising dates into an ISO string, setting defaults or helping with queries.
Example 2: When using Amazon Route53, you sometimes have to do a request, manipulate what you got back and then send a new bit of data. Instead a wrapper library around node-awssum which just helps you add or delete resource records would be much easier to use.
Example 3: A small wrapper around the Simple Queue Service means you could simply have some commands such as send(...), receive() and delete() would make using the service a breeze.
The reason for this is because the data structures it receives, and more especially those it returns, are far too complicated for dealing with them in your main program. Therefore in general, a wrapper library around these simple operations would make each service easier to use.
This library provides basic client functionality to each of these services. It's pretty simple but this means it's also quite powerful. In general you wouldn't use these libraries directly (though there is nothing stopping you making the odd call here and there, especially when setting your environment up) but instead you would use them via a more friendly API via a wrapper library.
You can use this library in your programs and applications, but it can also be built on for more user-friendly (from the perspective of the programmer) wrapper libraries.
Essentially it's a "data in, data out" kinda library without too many bells and whistles. It doesn't really check what you pass it, apart from when a parameter is required. As I sa
As a quick example, to create a domain in AWS SimpleDB:
var awssum = require('awssum');
var amazon = awssum.load('amazon/amazon');
var SimpleDB = awssum.load('amazon/simpledb').SimpleDB;
var sdb = new SimpleDB({
'accessKeyId' : 'my-access-key-id',
'secretAccessKey' : 'my-secret-access-key',
// 'awsAccountId' : 'my-aws-account-id', // optional
'region' : amazon.US_EAST_1
});
sdb.CreateDomain({ DomainName : 'test' }, function(err, data) {
console.log('Error :', err);
console.log('Data :', data);
});
A successful run puts the pertinent information into 'data' ('err' is undefined). An unsuccessful run results in a value in 'err' but nothing in 'data'.
Written by Andrew Chilton - Blog - Twitter.
Please see the CONTRIBUTORS file for all authors.
The MIT License : http://opensource.org/licenses/MIT
Copyright (c) 2011-2012 AppsAttic Ltd. http://appsattic.com/
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
NodeJS module to aid talking to Web Service APIs. Requires plugins.
The npm package awssum receives a total of 113 weekly downloads. As such, awssum popularity was classified as not popular.
We found that awssum demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.