Clojurians Log v2

This is certainly a non-goal for aws-api but it seems like the creds provider & client signing functionality could be pulled out into a separate, independent library.

We'd talked about this, @kenny. It's not so much a non-goal as it is a BFD because to make that work we have to define an API for other libraries to build against. The long term vision has always been that aws-api stays limited to providing access to AWS APIs based on AWS' descriptors, and other SDK-ish features live in other libraries.

Keep in mind that, given that we only have 2 ppl working on the library 1 day a week at the most, "long term" is definitely not next week or next month 😉

:thumbsup::skin-tone-2:

Finally got a signed request working & have started copying the bits out to get it to work independently of the internal aws-api api. It seems crazy to me that calling aws requires over 200 lines of non-trivial code!

I think they've really focused on making the SDKs work, which is how most ppl interact w/ AWS.

True. Curious why the rigmarole is necessary though. Most APIs don't require the sort of hoop jumping AWS does.