This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-10
Channels
- # announcements (1)
- # babashka (178)
- # beginners (216)
- # bootstrapped-cljs (1)
- # brompton (5)
- # calva (3)
- # chlorine-clover (1)
- # clj-kondo (2)
- # cljdoc (37)
- # cljfx (4)
- # cljs-dev (2)
- # clojure (360)
- # clojure-chile (8)
- # clojure-europe (3)
- # clojure-italy (5)
- # clojure-nl (9)
- # clojure-spec (2)
- # clojure-sweden (1)
- # clojure-uk (61)
- # clojuredesign-podcast (1)
- # clojurescript (83)
- # clr (2)
- # conjure (4)
- # core-async (14)
- # cursive (20)
- # data-science (2)
- # datomic (15)
- # docker (11)
- # emotion-cljs (1)
- # figwheel-main (28)
- # find-my-lib (1)
- # fulcro (46)
- # helix (16)
- # honeysql (14)
- # jobs (10)
- # jobs-discuss (17)
- # joker (1)
- # juxt (9)
- # kaocha (8)
- # leiningen (3)
- # meander (3)
- # news-and-articles (1)
- # off-topic (110)
- # pathom (7)
- # pedestal (4)
- # protojure (2)
- # re-frame (12)
- # reagent (25)
- # ring (4)
- # shadow-cljs (109)
- # spacemacs (9)
- # specter (1)
- # sql (3)
- # tools-deps (23)
Hi, we might need to transfer an existing datomic cloud system to a new aws account. What is the best way to handle that?
When deploying a Datomic HTTP direct endpoint, the final step in creating an API gateway says: > Enter your `http://$(NLB URI):port/{proxy}` as the "Endpoint URL". This NLB URI can be found in the Outputs tab of your compute or query group https://console.aws.amazon.com/cloudformation/home#/stacks under the "LoadBalancerHttpDirectEndpoint" key The value in my CF Outputs tab is formatted like this "http://entry.my-datomic-system-name.us-west-2.datomic.net:8184". If I were to follow the docs exactly, I would end up with a Endpoint URL that looks like this: http://http://entry.my-datomic-system-name.us-west-2.datomic.net:8184/{proxy}. I'm assuming that is not what the docs wanted, correct?
@kenny You can watch the video tutorial on http direct for more clear instructions. Definitely don't do http://http://...
I didn't 🙂 Following the docs verbatim would lead to that URL. Surprised it wasn't caught. Not really a huge fan of video docs...
Any idea why all calls to a Datomic http direct endpoint result in a 500 with this response?
{
"message": "Internal server error"
}
The API gateway logs end with a very unhelpful error.
Execution failed due to configuration error: There was an internal error while executing your request
I've seen that error before when I was working on creating an http-direct deployment and, in fact, I did misconfigure it. You're totally right that it isn't hitting datomic.
Watched the video. I have followed the steps exactly & still get the 500 :thinking_face:
Full example logs:
Execution log for request 6c5c6e23-0d88-4ac3-a160-374fc3842a83
Wed Jun 10 23:11:17 UTC 2020 : Starting execution for request: 6c5c6e23-0d88-4ac3-a160-374fc3842a83
Wed Jun 10 23:11:17 UTC 2020 : HTTP Method: POST, Resource Path: /datomic
Wed Jun 10 23:11:17 UTC 2020 : Method request path: {proxy=datomic}
Wed Jun 10 23:11:17 UTC 2020 : Method request query string: {}
Wed Jun 10 23:11:17 UTC 2020 : Method request headers: {}
Wed Jun 10 23:11:17 UTC 2020 : Method request body before transformations:
Wed Jun 10 23:11:17 UTC 2020 : Endpoint request URI:
Wed Jun 10 23:11:17 UTC 2020 : Endpoint request headers: {x-amzn-apigateway-api-id=eq2azct4a2, User-Agent=AmazonAPIGateway_eq2azct4a2, Host=}
Wed Jun 10 23:11:17 UTC 2020 : Endpoint request body after transformations:
Wed Jun 10 23:11:17 UTC 2020 : Sending request to
Wed Jun 10 23:11:17 UTC 2020 : Execution failed due to configuration error: There was an internal error while executing your request
Wed Jun 10 23:11:17 UTC 2020 : Method completed with status: 500
Everything appears correct. I wish aws had a bit more info as to what "configuration" could be causing this error.I can either https://docs.datomic.com/cloud/ions/ions-tutorial.html#orgef4cfed OR https://docs.datomic.com/cloud/ions/ions-tutorial.html#http-direct, right? I don't need to do the former to do the latter?