Add support for more services

[david-at-aws]

Add support for more services. Please comment here if you have one you'd like to see sooner rather than later.

[brackxm]

S3, DynamoDB

[david-at-aws]

Hey Michael, thanks for the suggestions!

S3 is very high on our priority list - it's a little bit trickier than other services though thanks to some historical quirks of the AmazonS3Client. It's definitely one of the services that we think will benefit the most from this style of API. The Glacier service, which maybe isn't that compelling on its own, was included in our first release mainly as a testbed for what eventual S3 support could look like. We're excited to get an actual S3 implementation in as soon as we can.

DynamoDB's also high on our priority list, but it needs some extra thought to make sure the Item "resource" gets modeled correctly. DynamoDB Items don't have straightforward identifiers, since which attribute(s) make up the primary key varies by table - that makes it tricky to do things like extracting a set of Item resources from a Query response that you can turn around and call update on. We're actively working on figuring this out and will hopefully have something to show in the near future!

[nigelcharman]

Elastic IP please (assuming it's not there already - I couldn't find it)

[mslinn]

Please support S3 and Elastic Transcoder soon. How about publishing your expected releases (milestones, RC, GA) for the various services that are being worked on?

[fulghum]

Thanks for the feedback Mike. Instead of drawing up specific milestones or a schedule for GA, we prefer to listen closely to what customers are asking for and prioritize our work based on that feedback. The more feedback and usage we get for the Resource APIs, the closer we'll get to GA, so please keep the feedback coming! ;-)

[mslinn]

Much more value would be provided if we had some idea what to expect. For example, we need to decide if we should duplicate your work in order to get a project finished quickly, or whether we should wait for a prerelease. Some guidance from you folks would be appreciated. At the minimum, please publish the method signatures that you are currently working towards. This would allow us to be more compatible with whatever the end result is.

[futurely]

Do you know how many active users and how much usage each service has? The services should be added according to their commercial value or popularity.

[trentrosenbaum]

I was just reading some older blogs and was looking for a lib like this. Are there any plans for move this forward. I like the presentation at re:invent 2014 and the resource api seemed really natural to use.