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
(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.
Oh, I assumed that "style guide" meant things like starting launch posts with "I'm excited to announce", providing a simple demonstration of how to use the service, including screenshots, including a customer quote if available, and ensuring that pricing and availability were clearly laid out.
There are, internally, and theyre pretty good. I always tried to use the AWS Docs style guide when writing internally, for example. Theyre specific on how to refer to products vs services vs features, which nouns to use, tone, grammar, etc.
PS: you might get tripped up on 0x00, 0x2F, or similar control characters? As i recall any valid octet can be included in a label. We definitely saw literal ‘*’ and ‘.’ inside labels. And I wouldnt be surprised to find a bell in there either.
> 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.
This is just the era of AWS (and amazon APIs). A lot of them look like SOAPy xml rpc because thats how they started, based on internal service frameworks. Check out SQS or S3 for similar examples.
Around 2010-11 there was a shift towards RESTish structures and json for serialization. A lot of methods and payloads still feel SOAPy, but look like json. I think it was DynamoDB which had the most unfortunate API with a literal xml-json transform live in the API service.
And then somewhere around 2015 you started seeing more well defined RESTish APIs with better tooling and adoption for smithy (and some openapi, iirc).
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.
I'll recommend dnscontrol as well, although the post is an unseasonal April fools joke, so helpful suggestions may be out of place.
The is-a.dev project uses dnscontrol to manage a subdomain registration service in GitHub, which is really clever. See https://github.com/is-a-dev/register
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.
I knew of GPG key signing parties, but never anything at this scale or impact. Might try booting the "Signing Computer Operating System Image Release coen-2.0.1" ISO in a VM and checking it out.
GuinansEyebrows | 13 hours ago
[0]https://banner.triweb.dev [1]https://news.ycombinator.com/item?id=39502097
inopinatus | 7 hours ago
ChiperSoft | 13 hours ago
cperciva | 13 hours ago
esseph | 13 hours ago
How many thousands or millions of employees does your org have? And how many projects deployed over the decades?
regularfry | 13 hours ago
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.
cperciva | 13 hours ago
colechristensen | 13 hours ago
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
stackskipton | 13 hours ago
mlhpdx | 13 hours ago
colechristensen | 13 hours ago
QuinnyPig | 10 hours ago
dbarlett | 13 hours ago
cperciva | 13 hours ago
(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.)
dbarlett | 12 hours ago
cperciva | 12 hours ago
As a non-Amazonian I've never seen it, of course.
jeffbarr | 7 hours ago
cperciva | 5 hours ago
donavanm | 3 hours ago
PS: you might get tripped up on 0x00, 0x2F, or similar control characters? As i recall any valid octet can be included in a label. We definitely saw literal ‘*’ and ‘.’ inside labels. And I wouldnt be surprised to find a bell in there either.
georgemcbay | 10 hours ago
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'.
cperciva | 9 hours ago
georgemcbay | 9 hours ago
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.
QuinnyPig | 6 hours ago
tonymet | 13 hours ago
threecheese | 12 hours ago
Stealing this. Gold lies at the intersection of cperciva and quinnypig.
donavanm | 3 hours ago
Around 2010-11 there was a shift towards RESTish structures and json for serialization. A lot of methods and payloads still feel SOAPy, but look like json. I think it was DynamoDB which had the most unfortunate API with a literal xml-json transform live in the API service.
And then somewhere around 2015 you started seeing more well defined RESTish APIs with better tooling and adoption for smithy (and some openapi, iirc).
YesThatTom2 | 12 hours ago
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
8organicbits | 6 hours ago
The is-a.dev project uses dnscontrol to manage a subdomain registration service in GitHub, which is really clever. See https://github.com/is-a-dev/register
cperciva | 3 hours ago
Not at all. Route 53 Files is a completely real service.
dougcalobrisi | 12 hours ago
https://doug.sh/posts/route53-as-a-key-value-store-2026-edit...
fr2029 | 10 hours ago
UltraSane | 10 hours ago
cbm-vic-20 | 10 hours ago
https://www.iana.org/dnssec/ceremonies/62
ecliptik | 8 hours ago
UltraSane | 8 hours ago
semiquaver | 9 hours ago
stackghost | 10 hours ago
ahachete | 6 hours ago
I see you are following the Dyna53 [1] steps ;) What a school of thought you have sparked, Corey!
[1]: https://dyna53.io/