Early last year, I published an article outlining the different options available for creating an enterprise-tailored hybrid DNS solution on AWS. This solution required EC2 instances, configuring DNS software, and a good amount of "undifferentiated heavy lifting."
As AWS has matured their enterprise offerings over the past several years, they've identified hybrid DNS as a gap and I was so happy to hear they've solved this problem by announcing the 'Route 53 Resolver for Hybrid Cloud' service today!
The new Route 53 resolver offering is broken down into two different offerings - an "inbound endpoint" and an "outbound endpoint". When used together, an enterprise has all of the pieces required to turn an existing DNS configuration into a hybrid configuration, bridging both the datacenter and AWS.
This post will review the functionality introduced in the new Route 53 Resolver for Hybrid Cloud offering, how to use it, and how to transition away from an EC2 based DNS forwarder solution to using only AWS' new managed Route 53 services!