Hacker News Reader

There are apparently many people managing their S3 Objects by hand but long to have them in a file system, yes.

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

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.

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'.

> 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?

Last job, we did for various control/audit reasons BUT it was all IaC and tickets.