-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Allow to bypass Route53 DNS record. #80
Comments
You may choose to not pass any domains. In such case, it will result in CloudFront's domain to be used. |
Considering Cloudfront is target alias, I really don't think you can simply plug-n-play different DNS server. You will need to create hosted zone on AWS and setup NS for it. Aka.
This results in you always having hosted zone on AWS as you cannot point other DNS server to Cloudfront's IP (as Cloudfront does not have IP). I hope I understood the request correctly, let me know. |
The use case would be, for example having The whole thing would llok something like this:
|
This does not seem like very reasonable pattern to be honest. I wouldn't recommend using CNAME for Cloudfront, seems like you are just going around setting up DNS properly. I cannot support this out of box as manual steps are required (setting DNS records on Cloudflare to validate certificate). Considering the focus on AWS and your scenario not being 100% automated, I'm gonna close this. Feel free to create stack without domain names and manually add them after creation via AWS Console. |
Related to #79.
Add a flag that will disable automatic Route53 record creation, so it is possible to use other DNS servers, or fallback to just adding the custom domain name to Cloudfront.
The text was updated successfully, but these errors were encountered: