This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-24
Channels
- # adventofcode (6)
- # announcements (4)
- # aws (21)
- # babashka (36)
- # beginners (58)
- # calva (3)
- # cider (2)
- # clj-kondo (21)
- # clojars (3)
- # clojure (35)
- # clojure-dev (4)
- # clojure-europe (5)
- # clojure-nl (8)
- # clojure-uk (8)
- # clojuredesign-podcast (7)
- # clojurescript (10)
- # core-async (3)
- # data-science (2)
- # datomic (2)
- # defnpodcast (11)
- # duct (4)
- # figwheel-main (1)
- # fulcro (34)
- # graalvm (12)
- # graphql (4)
- # joker (14)
- # kaocha (1)
- # midje (1)
- # off-topic (5)
- # pedestal (1)
- # re-frame (3)
- # reagent (4)
- # reitit (1)
- # shadow-cljs (4)
- # testing (12)
I've just published https://blog.jakubholy.net/2019/secure-repl-for-aws-fargate-services/ Feedback and improvements welcome! Also, Merry 🎄!
Thank you! I've now fixed links to the Tf modules
Trying to use the Cognitect aws-api
project to interact with S3. I can invoke ListBuckets
however if I try anything else like ListObjectsV2
or PutObject
all I get back is:
{:cognitect.anomalies/category :cognitect.anomalies/fault,
:cognitect.aws.client/throwable nil}
Does anyone know how I can get more information to see what’s failing?
(def s3 (aws/client {:api :s3 |
:credentials-provider (credentials/basic-credentials-provider
creds)}))
(aws/invoke s3 {:op :ListBuckets})
<correct response>
(aws/invoke s3 {:op :ListObjectsV2 :request {:Bucket "valid-bucket-name"}})
{:cognitect.anomalies/category :cognitect.anomalies/fault,
:cognitect.aws.client/throwable nil}
US West (N. California)
I have not set the region anywhere, didn’t think I needed to because ListBuckets
worked with out it. I’ll try setting it in the client constructor.
in general if you are running in AWS (EC2, Lambda, ECS) the client ctor doesn't need any options because everything is autodiscovered
Adding :region "us-west-1"
to the client constructor did the trick. Thanks @ghadi!