Wait, there's an official style guide?

(In all seriousness, I've been reading AWS launch posts for 20 years; this one was mainly imitating the S3 Files launch post but I diverged by adding the customer quote and the FAQ -- because of course I started this process with a PRFAQ, and some of the questions in the FAQ are legitimately important.)

> cperciva has internalized the AWS blog style guide better than most Amazonians

A little bit of Canadian/non-American English slipped in (eg. enrol, behaviour), which AFAIK would have been flagged for a real Amazon post because as Americans we were brave enough to get rid of the 'U' in a lot of British words, like 'colour' and 'armour'.

But by God, we kept the British 'U' in the word 'glamour'.

You might note who the customer quote is from.

to be fair, it's also that just with some severe restrictions on filenames

And route53 makes DNSSEC very easy to enable so all the DNS data is cryptographic signed. This makes putting public keys and certificates in DNS much more sensible.

neat, thanks

There are apparently many people managing their S3 Objects by hand but long to have them in a file system, yes.

I don't think this is there to satisfy "need".

But "automation" with this could legitimately (well, mostly) be based on a git repo with an s3files mount inside it. And a cron job, if you really want to get fancy.

Last job, we did for various control/audit reasons BUT it was all IaC and tickets.

This is... well it's mostly a joke. It's funny but you can indeed use and interact with DNS as a file store or have a file system based control over records.

Both DNS and S3 or any filesystem really... they're just key/value stores.

DNS also has considerably higher reliability and compatibility than almost anything else

> Are there that many people managing their dns by hand that they need this?

How many thousands or millions of employees does your org have? And how many projects deployed over the decades?