Hey @U0VP19K6K does your endpoint really have the proxy port? If you're in cloud your ion won't need the proxy port. What version of Datomic Cloud are you using?

I would audit all your ion calls to client and make sure they are all valid. And confirm you don't have dev-local or on-prem api's deployed with your code.

We’re a bit old 616-8879 (upgrading is another task)

I’m busy refactoring so I may well have mangled the config.

Sorry, TBC I get the above error when creating the client

@U1QJACBUM does datomic.cloud.client.local$create_client seem to imply that dev-local dep is ending up in the classpath (that final .local)?

The Cloudformation EndpointAddress output matches what I posted above, i.e. it includes the port

When you say “don’t have dev-local or on-prem api’s deployed with your code” you mean they’re not included in our deps.edn and are thus not in the classpath on the ion instance then I think I can confirm that they are not. I found a classpath printout in the “IonHttpDirectStarted” event and they do not appear there (though I couldn’t find any client api dep at all though)

@U0VP19K6K sorry! The endpoint should be correct for your version. Can you share your deps.edn?

Also does this error happen when you deploy and get a client, or when you try to get a client after deployed? Can you use the same map to connect locally? Do you get the map from env vars?

I suspect that get-param might not be returning what you expect.

Thanks Jaret. If anyone comes across this, it’s addressed here https://docs.datomic.com/cloud/troubleshooting.html#assert-failed

nvm I'm going back to the drawing board concerning the python part 😛

you can always deploy a datomic Ion that transacts information, then invoke it from python

as in over http, lambda, or hooking up the ion to a sqs queue - the world is your oyster

but you can't / shouldn't want to connect to datomic cloud directly from python

btw the rest API was an on-prem (not cloud) facility

ah