This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-22
Channels
- # announcements (7)
- # babashka (17)
- # beginners (45)
- # biff (2)
- # cider (16)
- # clj-on-windows (3)
- # cljs-dev (12)
- # clojure (27)
- # clojure-austin (1)
- # clojure-europe (18)
- # clojure-norway (5)
- # clojurescript (36)
- # conjure (35)
- # core-async (2)
- # datascript (4)
- # datomic (4)
- # emacs (15)
- # fulcro (23)
- # holy-lambda (12)
- # hyperfiddle (1)
- # introduce-yourself (5)
- # nbb (11)
- # off-topic (37)
- # pathom (34)
- # pedestal (9)
- # reitit (4)
- # releases (1)
- # remote-jobs (1)
- # sci (5)
- # scittle (3)
- # shadow-cljs (88)
- # tools-build (4)
what is the best way to call aws from in a lambda? I like cognitect-aws but for the bb target idk if it would work
It will work.
There is a bb pod for this and as far as I remember there is also a cognitect-api fork that is compatible with babashka (no pod is required).
In terms of a way to do a call to AWS from a lambda it’s extremely straightforward. Use the pod as you would do it locally and add all the required service permissions to Lambda (for instance via cloudformation).
As as an AWS template as you probably already pack your library dependencies.
If you go through bb HL tutorial you learn how to create a layer for your bb deps (bb resolved libraries). To have a pods working you simply copy the definition of a layer, then point to a location where HL stores pods, change the name of the layer (template.yml) and reference the ARN of the layer in the definition of the lambda (template.yml).
Here you can find a location of a pods: https://fierycod.github.io/holy-lambda/#/cli?id=cli-paths
You can download them if you set them first in project HL options:pods in bb.edn. In the documentation you can find that the command which downloads both the pods and deps is bb hl:babashka:sync
@U3JH98J4R please let me know if it helps ;)