This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-26
Channels
- # announcements (10)
- # asami (15)
- # babashka (200)
- # beginners (48)
- # calva (56)
- # cider (6)
- # clara (2)
- # cljs-dev (18)
- # cljsrn (6)
- # clojars (3)
- # clojure (23)
- # clojure-czech (2)
- # clojure-europe (41)
- # clojure-germany (5)
- # clojure-italy (19)
- # clojure-nl (5)
- # clojure-uk (8)
- # clojurescript (60)
- # clojureverse-ops (5)
- # cursive (14)
- # datomic (6)
- # events (1)
- # figwheel-main (5)
- # graalvm (17)
- # honeysql (2)
- # instaparse (1)
- # integrant (9)
- # jobs (5)
- # music (2)
- # off-topic (37)
- # other-languages (1)
- # pathom (10)
- # proletarian (5)
- # quil (3)
- # reagent (39)
- # reitit (4)
- # remote-jobs (3)
- # reveal (6)
- # rum (9)
- # shadow-cljs (27)
- # vrac (3)
- # xtdb (5)
Is there any way to get to use "next gen" instance types in the my-cf template
# AWS instance type. See for
# a list of legal instance types.
aws-instance-type=t2.medium
as far as i can tell, the t2 machines are dated, while trying to use next gen throws an error, it doesn't recognize the typeNo. I opened a feature request on this recently. If interested, you can vote for it there https://ask.datomic.com/index.php/604/support-for-recent-aws-instance-types
Yeah, @U1DBQAAMB the on-prem template is provided as a convenience you can roll your own. Otherwise we'd have to include the new instance types in the next release with the template tooling.