aws-sign4, aws-elastic-transcoder & cloudfront-signer released

[cdornan]

Folks, today I realised that although I have been using my elastic-transcoder aws-extensions in a production context, I hadn't done anything with the code since mid-March, when it was pretty-much ready to go.

So today I re-spun the code as two extension packages:

• aws-sign4 for authenticating an AWS request with the Signature V4 protocol in the aws framework and
• aws-elastic-transcoder, which uses aws-sign4 to build an elastic transcoder interface.

AWS have since built out the elastic transcoder api but I thought it was important to just get it out. I was very pleasantly pleased by how easy it was to just make up these two packages which just hook into the current aws -- a huge validation of its design IMHO.

As this arrangement seems to be so natural and productive I am inclined to stick with it. I consider it a part of the aws.

Have you considered moving a more module package structure? The design seems clearly to support it.

I have also published cloudfront-signer for signing CloudFront URLs. This is a fairly simple (if dead useful) standalone component without any dependencies on the aws package. It does live in module that fits with the aws scheme -- Aws.CloudFront.Signer -- and could be consider part of the aws family.

The current packages have been put out there on version 0.0.0.1 to get things moving. I expect to be revising them fairly quickly in light of feedback. They are all hosted on my personal github account (cdornan) but I expect to be re-housing them on the iconnect account soon.

[aristidb]

A more modular package structure might be a real Issue (with capital I). :D It's always something to consider indeed, I think both options have merits, the main reason why it's not right now is that the idea is that it makes maintenance easier.