This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-12-15
Channels
- # adventofcode (46)
- # announcements (3)
- # aws (7)
- # babashka (47)
- # beginners (86)
- # calva (40)
- # cider (8)
- # clj-kondo (22)
- # clojure (63)
- # clojure-europe (16)
- # clojure-hungary (3)
- # clojure-nl (1)
- # clojure-norway (46)
- # clojure-sweden (1)
- # clojure-uk (3)
- # clojuredesign-podcast (2)
- # conjure (4)
- # datalevin (1)
- # events (1)
- # fulcro (5)
- # graalvm (4)
- # honeysql (8)
- # hyperfiddle (15)
- # music (1)
- # off-topic (5)
- # pathom (7)
- # pedestal (1)
- # polylith (3)
- # portal (19)
- # quil (1)
- # re-frame (36)
- # releases (1)
- # specter (3)
- # sql (3)
- # timbre (11)
- # tools-deps (4)
- # xtdb (55)
has anyone used the Cognitect library with Digital Ocean Spaces? The Spaces product conforms to the S3 protocol and I have actually worked with it before in JavaScript using the JavaScript SDK, but some of the bucket/resource resolution stuff is different because it's not literally on AWS and I am having trouble getting the Cognitect library to talk to it
My setup looks something like this:
(def url "https://.nyc3.digitaloceanspaces.com")
(def s3 (aws/client {:api :s3
:credentials-provider (credentials/basic-credentials-provider
{:access-key-id access-key
:secret-access-key secret-key})
:endpoint-override {:hostname url}
:region "us-east-3"}))
This commands
repl> (aws/invoke s3 {:op :PutObject :request {:Bucket :Key "hello.txt" :Body "Hello world!"} })
yields
#:cognitect.anomalies{:category :cognitect.anomalies/fault,
:message "No known endpoint."}
https://github.com/cognitect-labs/aws-api/issues/150 have you seen this?
I did a Google check but embarrassingly did not find this. Looks like there's a workaround here, I'll try it. Thanks!