This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-19
Channels
- # announcements (5)
- # asami (7)
- # aws (10)
- # babashka (10)
- # beginners (49)
- # calva (12)
- # cider (5)
- # circleci (1)
- # clj-kondo (25)
- # clj-yaml (14)
- # clojars (5)
- # clojure (134)
- # clojure-europe (142)
- # clojure-france (3)
- # clojure-nl (1)
- # clojure-norway (4)
- # clojurescript (10)
- # cursive (8)
- # datomic (19)
- # emacs (11)
- # fulcro (8)
- # graalvm (29)
- # honeysql (7)
- # jobs (4)
- # jobs-discuss (9)
- # lsp (196)
- # obb (4)
- # off-topic (40)
- # pathom (4)
- # releases (4)
- # remote-jobs (3)
- # shadow-cljs (16)
- # sql (25)
- # squint (2)
- # tools-deps (12)
- # xtdb (7)
- # yada (4)
When cloudformation fails, is there a way to get the full logs? I see the events tab, but that seems to have only a very high level overview.
I don't see a link to any logs, maybe i have to set that up? Not sure why it wouldn't be on by default.
it helps to look at the resources status too, but I'm sure you knew that already
Maybe try https://docs.aws.amazon.com/cli/latest/reference/cloudformation/describe-stack-events.html? I haven't tried this before
Thanks @U032ZPU44KD! we tried describe-stack-events and it didn't give a more specific reasons then "resource failed to create" when we were hoping for "resource failed to create bc.... x"
Cloud trail events sometimes has more
Does that require setup? I don't see anything from the cloudformation browser console that looks like a link to cloud trail.
Cloudtrail events has everything that happens in an account. You can make custom trails and setup logging to cloudwatch etc, but you don't need it here. Between the stack events, the status of the resources in the stack, and cloudtrail events I can usually piece together what happened to a stack. Sometimes I need to look at the failed resource directly, assuming it managed to create it.
Thanks a lot for the response. 🙂 I'll want to automate enabling cloudtrail for everything then. And then turn it off after I'm done debugging. I can piece what happened together too, but I expect the stack trace to be available. If i can't get that, then i have a cloud service startup idea. 😆