4 ms·
Launching Route 53 Files
- GuinansEyebrows 1mo ago> Q. Is this HIPAA compliant? > A. Please do not store patient information in DNS. love this. reminds me a little of something else in the realm of DNS "hosting" posted to hn a few years ago [0][1] [0]https://banner.triweb.dev https://banner.triweb.dev [1]https://news.ycombinator.com/item?id=39502097 https://news.ycombinator.com/item?id=39502097
- inopinatus 1mo agocryptoshreddable via a KMS-wrapped DEK in the additional section, job done
- ChiperSoft 1mo agoAre 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.
- cperciva 1mo agoThere are apparently many people managing their S3 Objects by hand but long to have them in a file system, yes.
- esseph 1mo ago> 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?
- regularfry 1mo agoI 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.
- cperciva 1mo agoFiles which aren't DNS keys get ignored by Route 53 Files. So you could absolutely have a git checkout and update your DNS with 'git pull'.
- colechristensen 1mo agoThis 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
- stackskipton 1mo agoLast job, we did for various control/audit reasons BUT it was all IaC and tickets.
- mlhpdx 1mo agoAt first I thought this was a general purpose file system over R53, ala Corey Quinn. But my, what a gorgeously terrible idea. Well done.
- colechristensen 1mo agoto be fair, it's also that just with some severe restrictions on filenames
- QuinnyPig 1mo agoYou might note who the customer quote is from.
- deleted 1mo ago[deleted]
- dbarlett 1mo agoSpeaking as a former Blog Bar Raiser, cperciva has internalized the AWS blog style guide better than most Amazonians. This is spot-on.
- cperciva 1mo agoWait, 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.)
- dbarlett 1mo agoI 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).
- cperciva 1mo agoOh, 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. As a non-Amazonian I've never seen it, of course.
- jeffbarr 1mo agoActually, it is public -- https://www.linkedin.com/pulse/leadership-principles-aws-news-bloggers-jeff-barr/ https://www.linkedin.com/pulse/leadership-principles-aws-new... .
- cperciva 1mo agoOh, 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.
- tonymet 1mo agoAm I the only one who thinks that read() and write () (block based api) would be a poorer experience for managing key/value dns records?
- tonymet 1mo agoApparently so
- threecheese 1mo agoA “schema that reads like XML that learned JSON in prison” IM DEAD Stealing this. Gold lies at the intersection of cperciva and quinnypig.
- donavanm 1mo agoThis 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).
- YesThatTom2 1mo agoThis 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/ 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 https://github.com/DNSControl/dnscontrol/releases/tag/v5.0.0
- 8organicbits 1mo agoI'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 https://github.com/is-a-dev/register
- cperciva 1mo agounseasonal April fools joke Not at all. Route 53 Files is a completely real service.
- dougcalobrisi 1mo agoRoute53 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-edition/ https://doug.sh/posts/route53-as-a-key-value-store-2026-edit...
- fr2029 1mo agoneat, thanks
- UltraSane 1mo agoAnd 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.
- cbm-vic-20 1mo agoI dug into the DNSSEC rabbit hole a few weeks ago and got drawn into the fascinating root key signing ceremony. https://www.iana.org/dnssec/ceremonies/62 https://www.iana.org/dnssec/ceremonies/62
- ecliptik 1mo agoI 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.
- UltraSane 1mo agoIt really is something to behold. When you start storing FIPS 140-2 Level 4 HSMs offline inside safes you know things are serious.
- semiquaver 1mo ago
- stackghost 1mo agoFun! Reminds me of https://github.com/nathanvy/dnsbbs https://github.com/nathanvy/dnsbbs
- ahachete 1mo agoGood job, Colin. I see you are following the Dyna53 [1] steps ;) What a school of thought you have sparked, Corey! [1]: https://dyna53.io/ https://dyna53.io/
- cherioo 1mo ago> If the same record is changed in the file system and in Route 53 at the same time, we aim for last-write-wins. This is not strictly possible, since Route 53 does not expose modification timestamps on records Except route 53 provides a fully ACID transactional API you can build your own locks with!