Colin Percival ships Route 53 Files, an unofficial NFS filesystem over Route 53 records

Sources: primary, discussion
Summary: The post is written in AWS launch style and its FAQ states this is not an AWS service. Records act as files and alias records act as symlinks. The post states a write through Route 53 Files takes about 90 seconds to reach live DNS, and an external Route 53 change takes up to six minutes to appear in the mount. Those figures belong to Route 53 Files and the S3 Files stack the post says it sits on rather than to Route 53 itself, and the post cautions that reaching live DNS does not make a change visible worldwide because record TTLs and caching govern that.
Why it matters: The post is a working demonstration that a DNS zone is a general-purpose key-value store, with the propagation delay and the TTL caveat of using it that way stated in numbers rather than left implicit.