How many thousands or millions of employees does your org have?
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.
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
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. (A year ago I asked Gemini about a Vertex deployment and it was a mess going through two dozen weird circus tricks - none that worked). 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
(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.)
GuinansEyebrows•1h ago
[0]https://banner.triweb.dev [1]https://news.ycombinator.com/item?id=39502097