in a way that doesn’t end up into “Why I have to do all of this” 🙂

is aws-clj-sdk in a usable state? are there codox generated docs available

no & no

yesterday I got the 1st api call through but haven’t pushed yet and most APIs are not generated yett

and I haven’t inlined docs yet

so, soon… how can I help?

oops, meant for private chat 🙂

err 🙂

hmm well

apropos, what about the post support for portkey, I guess we’d need that for the demo next week

no you need it 😉

@viesti what’s the current state of your work towards POST? any blockers or doubt?

blocked but saw some light yesterday while watching basketball (long story)

if I have time to try the proxy approach I think that at first I’d make it work by passing :get params to function as now

then passing single input param for :post

don’t yet have idea for ring

@tatut a required task which is independent enough is: computing the endpoint. Data live there https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/resources/com/amazonaws/partitions/endpoints.json (missing from the repo at the moment) and mimicking aws-sdk-java logic would be a good start

@viesti get the proxy to work and I’ll guide you with ring

yes

I’ll try it out some day, the endpoint seems straight forward, but don’t hold your breath

http://docs.aws.amazon.com/cli/latest/userguide/cli-environment.html

> AWS_DEFAULT_REGION – AWS region. This variable overrides the default region of the in-use profile, if set.

and profiles are in ~/.aws/credentials, say region=eu-west-1 under the ini file sections, from which [default] is used by default if present, otherwise one that matches AWS_PROFILE environment variable if present

https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/java/com/amazonaws/regions/DefaultAwsRegionProviderChain.java

compat with env & credentials would be great

route53 seems to be rest-xml, not rest-json so defapi fails for it, in my test

the xml age

I even have removed defapi locally

but yeah focusing on rest-json atm

one protocol after the other

nice

totally untested but generation of rest-json api is ok

oh and all endpoints are wrong since hardcoded to lambda/frankfurt

anyway it looks like this https://github.com/portkey-cloud/aws-clj-sdk/blob/master/src/portkey/aws/lambda.clj

Step #4 and #5 sounds complex to emulate http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html

Step #4 is not that hard: From inside the container, you can query the credentials with the following command: Copy [ec2-user ~]$ curl 169.254.170.2$AWS_CONTAINER_CREDENTIALS_RELATIVE_URI Output: { “AccessKeyId”: “ACCESS_KEY_ID”, “Expiration”: “EXPIRATION_DATE”, “RoleArn”: “TASK_ROLE_ARN”, “SecretAccessKey”: “SECRET_ACCESS_KEY”, “Token”: “SECURITY_TOKEN_STRING” }

source http://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html