CloudFront alias in Route 53 private hosted zone


The Route 53 documentation says things like:

You can't create a resource record set in a private hosted zone to route traffic to a CloudFront distribution.


Alias resource record sets for CloudFront can't be created in a private zone.

But they can! Try it. It works. (If the Route 53 console doesn't suggest the alias target, you can still write it yourself.)

It makes sense if, for example, you're using a split zone setup.

Is the documentation mistaken, or is this not intended or guaranteed to work?

(My private hosted zone is in us-east-2.)

asked 10 months ago607 views
1 Answer

As this is DNS related and without testing myself, technically what you say is most likely true.

Cloudfront usually is publicly facing but technically you could create a private record to resolve to a cloudfront resource.

I guess if you have a split horizon DNS you would have to create a record in the private zone if resources need to resolve it.

profile picture
answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions