Best AWS lib?

130 views
Skip to first unread message

Stephen Handley

unread,
Oct 14, 2012, 7:33:23 PM10/14/12
to nod...@googlegroups.com
Was wondering if anyone has suggestions on an AWS lib to use in node that has good service coverage and is actively maintained

Among the ones I've found are:

node-aws looks good but is missing s3 coverage
aws-lib doesn't seem to be actively maintained 
node-awssum looks to have good coverage but high footprint due to its monolithic approach ("Node.js modules for talking to lots of Web Service APIs.")

I really liked using Boto in python and wondering what's the closest similar lib for Node.. any suggestions would be much appreciated. 

Andrew Stone

unread,
Oct 14, 2012, 7:38:41 PM10/14/12
to nod...@googlegroups.com
node-awssum works really well. It is a giant monolithic library, but I've used it successfully just with the AWS parts. Those are the oldest/most reliable and Andrew Chilton is very responsive and actively maintains that library.

-Andrew

--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Andrew Chilton

unread,
Oct 15, 2012, 4:03:40 AM10/15/12
to nod...@googlegroups.com
Hi Stephen,

On 15 October 2012 12:33, Stephen Handley <stephen...@gmail.com> wrote:
> node-awssum looks to have good coverage but high footprint due to its
> monolithic approach ("Node.js modules for talking to lots of Web Service
> APIs.")

The good news is that AwsSum lazily loads whatever modules you need.
So for example if you need S3 you load up the awssum.js, amazon.js and
s3.js files - all of the rest are not loaded unless you specifically
do it. :) I hope that eases your worry about the footprint - in
reality it's very little code loaded. e.g.

var awssum = require('awssum');
var amazon = awssum.load('amazon/amazon');
var S3 = awssum.load('amazon/s3').S3;

Also, AwsSum has a new docs site so please take a look here. It
desperately in needs more examples but I am adding those over time.
Also the docs are now being generated from the actual code (to save me
lots of time) so everything should be in order.

* http://awssum.io/

Feel free to email me if you have any questions - I'm more than happy
to help (for anyone, not just you Stephen). :)

Cheers,
Andy

--
Andrew Chilton
e: chi...@appsattic.com
w: http://appsattic.com/
t: https://twitter.com/andychilton

Andrew Chilton

unread,
Oct 15, 2012, 4:11:24 AM10/15/12
to nod...@googlegroups.com
Hi Andrew,

On 15 October 2012 12:38, Andrew Stone <andrew.j...@gmail.com> wrote:
> node-awssum works really well. It is a giant monolithic library, but I've
> used it successfully just with the AWS parts. Those are the oldest/most
> reliable and Andrew Chilton is very responsive and actively maintains that
> library.

It's not really monolithic (see my previous post) but it is big
because Amazon have 25 or so services! AwsSum now has 100% coverage of
all of these services, though there are a few recent additions I need
to add in. Other packages like aws-lib have just implemented the
services that use Signature v2 whereas AwsSum can do Signature
versions v2, v3, v4 and use STS tokens which covers all services.

Thanks for your kind comment about being responsive however there are
a few issues I need to go and fix! :)

In other news AwsSum celebrated it's first commit a year ago
yesterday. It's been a good year so far, here's to the next (OpenStack
is next on the list). :)
p: +64 21 891 681

Mikeal Rogers

unread,
Oct 15, 2012, 7:07:16 AM10/15/12
to nod...@googlegroups.com
if you just want to make some API calls or do some streaming, request supports AWS signing. I use it all the time.

-- 
Mikeal Rogers
Sent with Sparrow

Andrew Chilton

unread,
Oct 15, 2012, 2:48:14 PM10/15/12
to nod...@googlegroups.com
On 16 October 2012 00:07, Mikeal Rogers <mikeal...@gmail.com> wrote:
> if you just want to make some API calls or do some streaming, request
> supports AWS signing. I use it all the time.

Request is certainly a good way to go if you want to call some simple
operations. However, request supports only one version of the AWS
Signature (v2) which rules out half of Amazon's services.

Also, if you need to create fairly complex requests with XML bodies
and suchlike then you'll have to make those yourself, whereas AwsSum
is designed to help you with all this. Of course your choice will
depend on your use-case and between all of these libraries there
should be something which makes sense to you.

Stephen Handley

unread,
Oct 24, 2012, 2:30:39 PM10/24/12
to nod...@googlegroups.com
Thanks for the responses and sorry for the delay in responding. 

Yeah, I'm definitely looking for a boto-style lib with full coverage of Amazon's services so it can be used for automation. Looks like at this point awssum is the way to go. Will make sure to keep an eye on node-plata as that develops.

Andrew, thanks for the info on lazy loading. I appreciate that approach but have to admit I'd rather see the package dedicated purely to AWS with the other stuff (Twitter, OpenStack) in separate npm modules. What's the rationale for keeping it all in a single package? 

Stephen
Reply all
Reply to author
Forward
0 new messages