Deploying to heroku was a snap, but I’m trying to get wild and deploy to AWS Lambda - and I feel like what I need is a handler with resolved dependencies - if there is such a thing

I was thinking I could do something like (ig/init config [:duct.core/handler])

But that does not appear to be a handler I can invoke with a request

I haven’t actually used AWS Lambda so I’m not sure what’s involved.

https://github.com/mhjort/ring-apigw-lambda-proxy#usage

The code snippet in that section may be a good indicator?

And the deflambda macro: https://github.com/uswitch/lambada/blob/master/src/uswitch/lambada/core.clj#L4

certainly not a show stopper for many, but the price tag for lambda is too appealing 🙂

as I figure out my way around duct, I would love to write up a module or something to give back

You could probably do something like:

(deflambdafn blah [in out ctx]
  (:foo.lambda/blah (ig/init config [:foo.lambda/blah])))

But perhaps there’s a way of ensuring that the config doesn’t need to be reinitialised?

Something to investigate I guess. Lambda functions don’t appear to be directly compatible with Ring handlers.

👌

I will keep digging! Thank you

(let [f (:foo.lambda/blah (ig/init config [:foo.lambda/blah]))]
  (deflambdafn ...

Perhaps it works with a let? No idea 🙂

would an atom work? store the result of (ig/init)?

Yeah, you could cache it? But a let might be a better idea…

Awesome - that gives me something to go on

Thank you so much

np