worked a little bit today by integrating aws test suite for signing v4

not finished, I’ll find some time this week to continue on this one

hum, I’m a bit puzzled that all API’s don’t support v4 signature

a thought: could we do with just java.net.URLConnection (and something that’s available on cljs)?

since we have async support (https://github.com/portkey-cloud/aws-clj-sdk#coreasync), dropping clj-http would fill the other goal of the newer java sdk (https://github.com/aws/aws-sdk-java-v2#new-features-for-developer-preview)

that’s a great idea @viesti

It’s not only about getting rid of the lib, but clj-http and the wrapper stuff that it brings is hard to hack

and I don’t exactly why they don’t support v4 signs for all apis

ah, true the clj-http middleware worries, don’t have good idea on http://java.net version though, would need a poc