This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-04
Channels
- # architecture (20)
- # aws (8)
- # beginners (13)
- # boot (9)
- # cider (80)
- # cljs-dev (69)
- # cljsrn (7)
- # clojure (243)
- # clojure-dusseldorf (8)
- # clojure-italy (5)
- # clojure-norway (3)
- # clojure-poland (57)
- # clojure-russia (10)
- # clojure-shanghai (2)
- # clojure-spec (11)
- # clojure-uk (50)
- # clojurescript (198)
- # core-async (11)
- # crypto (2)
- # cursive (14)
- # datomic (17)
- # figwheel (8)
- # garden (7)
- # hoplon (8)
- # incanter (4)
- # jobs (1)
- # leiningen (1)
- # liberator (38)
- # lumo (28)
- # om (55)
- # onyx (10)
- # pedestal (13)
- # perun (20)
- # re-frame (1)
- # reagent (16)
- # ring-swagger (9)
- # spacemacs (11)
- # test-check (9)
- # unrepl (43)
- # untangled (163)
- # yada (8)
I have a problem getting amazonica to list my cloud formation stacks (cf/list-stacks) I’m able to list them with the aws cli and I can list my s3 buckets with amazonica (so I don’t think its a permissions error). All I get back is {:stack-summaries []} … any ideas? Thanks in advance.
@juliobarros are you looking at the right region?
Hmm … the aws cli works so I thought it would ‘inherit’ all the same settings.
The config is set to the right region.
@l0st3d You were right. I wrapped an explicit with-credential around it and got my stacks. … I wonder how the region is set and why it works for S3 and not cloudformation.
@juliobarros amazonica is a bit inconsistent about using :region and :endpoint ... I think it comes from the underlying aws lib, and the fact that s3 is so old now 😉
was just about to find some code where i had done that sort of thing and work out what i did ... but then you worked it out 😉
Thanks. I didn’t mention that it also works with (cf/list-stacks {:endpoint “us-west-2”})