This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-18
Channels
- # announcements (31)
- # asami (11)
- # aws (33)
- # babashka (30)
- # beginners (69)
- # calva (1)
- # chlorine-clover (10)
- # cider (3)
- # clj-kondo (24)
- # cljdoc (19)
- # cljs-dev (1)
- # cljsrn (2)
- # clojure (104)
- # clojure-australia (4)
- # clojure-dev (29)
- # clojure-europe (202)
- # clojure-germany (36)
- # clojure-nl (6)
- # clojure-poland (3)
- # clojure-serbia (6)
- # clojure-spec (18)
- # clojure-uk (32)
- # clojurescript (36)
- # conjure (1)
- # core-async (6)
- # crux (28)
- # datomic (15)
- # duct (1)
- # emacs (11)
- # fulcro (24)
- # graalvm (12)
- # jobs (3)
- # juxt (1)
- # kaocha (2)
- # keechma (4)
- # lsp (1)
- # malli (102)
- # meander (17)
- # off-topic (16)
- # pathom (8)
- # re-frame (12)
- # remote-jobs (7)
- # rewrite-clj (72)
- # shadow-cljs (27)
- # sql (26)
- # tools-deps (8)
- # vim (3)
- # yada (5)
(s3/put-object
:endpoint ""
:bucket-name "humboi-videos"
:key thumbnail-name
:file "./resources/public/thumbnail.png"
:access-control-list {:grant-permission ["AllUsers" "Read"]})
What I want to know is how much progress has been made in putting the object in the bucket. For example if the total data is 1000 bytes, I want to know how many bytes has been uploaded to the s3 bucket. How can I achieve this?
there is no solution out of the box. But with some effort you can write it yourself. The trick is to upload :input-stream
instead of :file
where the input stream would be a proxy that notify about how much data was consumed
like in this question https://stackoverflow.com/questions/1339437/inputstream-or-reader-wrapper-for-progress-reporting
I’m uploading a jar on Elastic Beanstalk. The lein project was created using #luminus. The jar is created with lein uberjar and when run on the local machine works fine, i.e., requests to localhost:3000 work fine. But when I upload the jar on Elastic Beanstalk on the java platform, I’m getting a 502 Bad Gateway on the app link. How do I fix this?
Never used EB, but according to these docs - you need to listen to port 5000 https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-se-nginx.html
@U0JEFEZH6 what do you use instead of eb?
@U0JEFEZH6 changing to 5000 didn’t work. Getting the same error
Digging through docs should help, as I mentioned - never used it, but the setup is pretty clearly explained.
@U0JEFEZH6 is there a reason you chose ecs + fargate rather than elastic beanstalk?
We have dozen or so Clojure services and we've been using Docker for last 4 year or so. Autoscaling is not a requirement, and ECS can guarantee that the system stays up in rare case of something shutting down
@U0JEFEZH6 just curious. What was the previous setup?
Terraform + Ansible + Google Cloud platform VMs. Became too manual to maintain, even though it was simple to operate. ECS+Fragate is working great for us, never had issues with it and we're Ansible-free. Everything is stored as code and cleanly setup.
AWS docs have a lot of resources explaining how to get started, including the copilot tool that they released not long ago. Not sure if it's learnable, like a programming language- there's way more moving parts (IAM, AWS networking, Docker itself and more).
Lambda has nothing to do with ECS/Fargate directly, as far as application deployments are concerned. Different tool
@U0JEFEZH6 have you ever used k8s with eks?
instead of fargate? I’ve heard that the provisioning with fargate isn’t reliable because cpu power can vary by a factor of 5
I think the problem is that the datomic access gateway needs to be run before the client can connect