Launching Route 53 Files

5 comments

• srvmshr 4 minutes ago
  I think its best usecase can be in agentic automation from what I can understand so far. I don't know if this is the correct read on the design choice.

  If models/agents don't have to learn the various Route 53 & DNS API, and (with some guardrails) execute DNS jobs looking at it like a filesystem, it could make deployment automation quite simpler - and less prone to looping over wild esoteric solutions. FWIW a lot of the final knob pushes still require someone using a browser & clicking bunch of buttons. This simplifies it. "Everything is a file in UNIX" idea, but carried over to DNS & resource management
• dbarlett 3 minutes ago
  Speaking as a former Blog Bar Raiser, cperciva has internalized the AWS blog style guide better than most Amazonians. This is spot-on.
• mlhpdx 20 minutes ago
  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.
  [-]
  • colechristensen 18 minutes ago
    to be fair, it's also that just with some severe restrictions on filenames
• ChiperSoft 45 minutes ago
  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.
  [-]
  • stackskipton 12 minutes ago
    Last job, we did for various control/audit reasons BUT it was all IaC and tickets.
  • regularfry 31 minutes ago
    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.

    [-]
    • cperciva 25 minutes ago
      Files 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'.
  • cperciva 43 minutes ago
    There are apparently many people managing their S3 Objects by hand but long to have them in a file system, yes.
  • colechristensen 22 minutes ago
    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
  • esseph 33 minutes 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?
• GuinansEyebrows 48 minutes 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 [1]https://news.ycombinator.com/item?id=39502097