Fork me on GitHub

looking for my cloud system endpoint, when I do aws cloudformation describe-stacks --stack-name <name> the only output that sounds like endpoint is this:

                    "OutputKey": "EndpointAddress",
                    "OutputValue": "",
                    "Description": "Stable entry address"

✔️ 1

That outputvalue is your endpoint. You can also see your system endpoint the outputs tab. Specifically under the ClientApiGatewayEndpoint key. As a side curiosity, what version of Datomic Cloud are you using?


on older versions of Datomic cloud the endpoint takes the format of:



should be the newest I selected from the top of the list in the marketplace configure


ah I guess I should have used "production" instead of "solo"


@U02CV2P4J6S If you are looking to upgrade. Might I suggest that you use our split stack instructions and move to separate production templates on the latest.


The allows you to choose smaller instances to get the lower price of the "solo" template when we had the bifurcation. Marketplace does not allow us to remove the option for any users who were previously subscribed to select the solo topology even though it is now moot.


I see. Now I already launched a production on next to the solo one. Guess I check the split thing


Yeah I think you should upgrade to the production template and follow our docs, reading split stack page. I'd be happy to jump on a call to discuss.


If you don't care about anything you made with the solo, I can also walk you through completely deleting.


fixed btw - awesome

Daniel Jomphe19:11:15

Dear Cognitect Datomic team, here's a renewed plea for a production-grade Datomic Cloud Backup &amp; Restore solution. Here we relied on the nice efforts by Tony Kay with some success, but we now see our fate is truly and only in your hands.


btw we use this for datomic cloud backups


we actually wrap it in another, our ops-specific tool that does some other niceties like opening datomic-cloud proxies from dev machines:

Daniel Jomphe19:11:01

Thanks vlaaad. Wanderung is intriguing, and it's nice to have your gitops util to look at.

Daniel Jomphe19:11:38

Do you feel like it satisfies all normal requirements? E.g. • truly coherent remapping of IDs (obviously) in the new DB • capability to clean up PII when restoring to a non-prod DB


I think @UB95JRKM3 might provide more insight into this. What do you mean by coherent remapping?


db ids are different between backups/restores, but they represent the same data graphs


there are sanity checks for this stuff there


our datomic usage is a bit weird, since we use it as a "git" of sorts with history being a part of publicly exposed API (although wrapped so customer don't know about db ids and txs)


because of that, we have separate databases for edits and what is available to users in prod, and we copy and restore them between internal edits and prod read-only dbs, so we actively use the copying/restoring feature, and so far it seems to work fine


one thing to be aware of is that we can afford to hold all datoms in memory, so it might not be optimized for backups of big databases...

Daniel Jomphe21:11:47

Ok, you answered all the questions I had (including DB id coherency). Thanks again!


@U0514DPR7 plea heard. We are working on it.

👏 4
🚀 2
Daniel Jomphe15:11:39

Thanks for letting us know, Stu! 🎉


@U072WS7PE what would be really nice is some kind of time estimate. Some of us have regulators to satisfy, and “it will happen sometime in the future” is not a comfortable position to be in.