alt Hacker NewsLaunching Route 53 Files
Comments
At first I thought this was a general purpose file system over R53, ala Corey Quinn. But my, what a gorgeously terrible idea. Well done.
A “schema that reads like XML that learned JSON in prison” IM DEAD
Stealing this. Gold lies at the intersection of cperciva and quinnypig.
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.
https://doug.sh/posts/route53-as-a-key-value-store-2026-edit...
Good job, Colin.
I see you are following the Dyna53 [1] steps ;) What a school of thought you have sparked, Corey!
[1]: https://dyna53.io/
> Q. Is this HIPAA compliant?
> A. Please do not store patient information in DNS.
[0]https://banner.triweb.dev [1]https://news.ycombinator.com/item?id=39502097
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.
Fun! Reminds me of https://github.com/nathanvy/dnsbbs
Am I the only one who thinks that read() and write () (block based api) would be a poorer experience for managing key/value dns records?
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.
https://github.com/DNSControl/dnscontrol/releases/tag/v5.0.0
Speaking as a former Blog Bar Raiser, cperciva has internalized the AWS blog style guide better than most Amazonians. This is spot-on.