DNS configuration management
A Route 53 proposal puts machine configuration in DNS records, using lookups in place of tools such as Puppet, Ansible, or Chef.
This approach uses Amazon Route 53 records as configuration data. Applications can read settings from DNS rather than from a separate configuration service.
DNS offers a distributed read path and simple replication, but also inherits DNS caching and update delays. Those properties must be part of the design.
Primary source: https://www.lastweekinaws.com/podcast/aws-morning-brief/whiteboard-confessional-route-53-db/