(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.)
I left 18 months ago, so my memory is a bit fuzzy, but there was at least an overall style guide, one for each post type (e.g. a launch announcement), and the style for procedures (inherited from AWS Docs).
Oh, I was being facetious. I'm pretty sure Jeff mentioned needing to spend time writing a style guide when he started having other Amazonians write posts for "his" blog.
> 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'.
Yeah, I was aware of those... but I just couldn't bring myself to write American, especially in the current political climate. You can consider those a non-tariff trade barrier.
As a heavily disaffected American (who still can't wrap his head around the fact that we let this happen twice) I support any form of protest against us.
Route53 makes a great, simple, HA key-value store for some use cases. I've used it in GitHub Actions when nothing else was easily available to store values and put a little post together explaining how a while back. For many things, there isn't a reason for more complexity.
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.
Are there that many people managing their dns by hand that they need this? Outside of various txt records, most of my domains are mapped to specific resources via automation.
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.
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
This is FANTASTIC! I laughed so hard I nearly fell out of my chair.
Have you seen DNSControl?
If you want a serious alternative to the Route53 API, there's an open source project called https://dnscontrol.org/ DNSControl. It's like Terraform for DNS but it doesn't suck like Terraform.
Version v5.0 just shipped. It's a major rewrite that makes it much more extensible.
(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.)
As a non-Amazonian I've never seen it, of course.
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'.
As a heavily disaffected American (who still can't wrap his head around the fact that we let this happen twice) I support any form of protest against us.
Stealing this. Gold lies at the intersection of cperciva and quinnypig.
https://doug.sh/posts/route53-as-a-key-value-store-2026-edit...
https://www.iana.org/dnssec/ceremonies/62
[0]https://banner.triweb.dev [1]https://news.ycombinator.com/item?id=39502097
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.
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
How many thousands or millions of employees does your org have? And how many projects deployed over the decades?
Have you seen DNSControl?
If you want a serious alternative to the Route53 API, there's an open source project called https://dnscontrol.org/ DNSControl. It's like Terraform for DNS but it doesn't suck like Terraform.
Version v5.0 just shipped. It's a major rewrite that makes it much more extensible.
https://github.com/DNSControl/dnscontrol/releases/tag/v5.0.0