Fork me on GitHub
#datomic
<
2020-06-11
>
marshall00:06:01

Correct. Did you set up a vpc gateway?

kenny00:06:23

And it is available.

marshall00:06:33

What address did you usr

kenny00:06:58

Where do I provide an address?

marshall00:06:30

Or rather did you choose the correct nlb

marshall00:06:57

And is this latest version of datomic

kenny00:06:59

There is only 1 production topology deployed in this account & Datomic is the only service using NLB.

kenny00:06:29

Ooo, it is not the latest. It is a version that should have http direct support. It's on 616 8879.

kenny00:06:51

Will try updating to the latest version to see if that helps.

marshall00:06:13

yeah, that should have it

marshall00:06:53

what’s in your ion-config ? @kenny you need to have a valid :http-direct key in there for Datomic to start the http direct listener

kenny00:06:12

{:allow [],
 :lambdas
 {:query-pricing-api
  {:fn cs.ions.pricing-api/lambda-handler,
   :description "Query the pricing-api.",
   :concurrency-limit 100}},
 :http-direct {:handler-fn cs.ions.pricing-api/web-handler},
 :app-name "datomic-prod-v2"}

marshall00:06:07

can you look for "IonHttpDirectStarted" in your Cloudwatch logstream

marshall00:06:13

for the production system

kenny00:06:31

Sure. I think it's not there. Not super familiar with CloudWatch Logs.

marshall00:06:48

include the double quotes

marshall00:06:19

are you sure your system is actually starting up?

kenny00:06:23

This application has been deployed, if that's your next question 🙂

kenny00:06:38

The latest deployment did not fail.

marshall00:06:40

i.e. can you connect via the bastion

marshall00:06:50

with a repl or whatever

kenny00:06:08

Yep, I can get a client back.

kenny00:06:24

& call list-databases.

kenny00:06:30

Updated to 668 8927 and still getting the same 500.

kenny00:06:02

New deploy was successful & same error.