Read tbray's article looking for QLDB. There were keywords along the way suggesting the possibility, but it didn't get there. As a NYC financial services CTO,

Read tbray's article looking for QLDB. There were keywords along the way suggesting the possibility, but it didn't get there. As a NYC financial services CTO, a few years back I spoke to Jassy personally, asking him to please not make 'traditional' blockchain nonsense, but to please productize and release a distributed ledger primitive. A few weeks later, AWS got back to us and said they were willing to work on such a thing, and a few groups (perhaps such as yours) jumped on as well. In our case, we were looking to use it to help manage multiparty contracts where we as a bank were trusted by the multiple parties who didn't need to trust each other. When AWS did eventually* announce AWS Blockchain at re:Invent, they announced QLDB alongside. One was what everyone was begging for, one was useful. I'll leave which is which as an exercise for the reader. :-) TL;DR: I encourage anyone serious about solving financial services problems where blockchain comes up to look at QLDB instead, but also anyone looking at security, compliance attestation, or other multi-party trust or regtech related problems. * Note: "eventually" as in, quite late to the blockchain hype party, and dragged kicking and screaming by the sales org, as tbray describes, so that at least they'd stay in the room with "big IT" signing up for IBMs hyperledger and other failed experiments.