41–50 of 183 posts
I'm pretty sure this is what most people actually want when they say they want a blockchain, they just don't know it yet. It's got all the useful database features with none of the "well uh let's distribute it over people's computers and let people mine coins to support it" complexity, which adds nothing to 99% of usecases besides silly ICO potential.
How can you make something like MakerDAO on a centralized ledger?
Did they just ship Trillian, or is this an AWS-exclusive design? The webpage says they use SHA256, but it doesn't go much more into detail than that.
AWS-Exclusive from my understanding. Not in AWS but from reading other comments, it sounds like this has been widely used internally for some time.
Earlier quoted context omitted.
Amazon could leak your secrets stored in Secrets Manager, or KMS. ACM could leak your private keys. EC2 hypervisor could have a 0day that allows China to steal all your data. CloudTrail could drop audit logs. At some point, you have to trust the company who's software you're using. Sure Amazon could easily drop the last N transactions, but what motivation do they have to do so? What behavior in the past makes you thi…
Completely agree - what I'm wondering is why they are telling their customers that they can verify the data for themselves, when that is entirely pointless: "and using cryptography, you can easily verify that there have been no unintended modifications to your application’s data"
If the digest you provide is found, then you know the data hasn't been changed. Sure, that's the only bit of information you get, but in a lot of cases that's the only one you need.
It doesn't guarantee your data can't be changed, no. What guarantees that is your contact with Amazon.
Earlier quoted context omitted.
They could, but why would they?
Indeed, they wouldn't - but the product offering sounds like they are telling customers that they can audit their data and that it is cryptographically verifiable - but why does the customer care about this, unless they don't trust amazon to preserve data integrity?
Earlier quoted context omitted.
The AWS conference is going on: https://reinvent.awsevents.com/
So?
Earlier quoted context omitted.
Completely agree - what I'm wondering is why they are telling their customers that they can verify the data for themselves, when that is entirely pointless: "and using cryptography, you can easily verify that there have been no unintended modifications to your application’s data"
How is it useless? If the digest you provide is found, then you know the data hasn't been changed. Sure, that's the only bit of information you get, but in a lot of cases that's the only one you need. It doesn't guarantee your data can't be changed, no. What guarantees that is your contact with Amazon.