Skip to content
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

Closed
pinarruiz opened this issue Feb 27, 2023 · 4 comments
Closed

[FR] Allow to bypass Route53 DNS record. #80

pinarruiz opened this issue Feb 27, 2023 · 4 comments
Labels
question Further information is requested

Comments

@pinarruiz
Copy link

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.

@sladg
Copy link
Owner

sladg commented Feb 27, 2023

You may choose to not pass any domains. In such case, it will result in CloudFront's domain to be used.
Afterwards, you can manually create whatever DNS records you need that will target Cloudfront.

@sladg
Copy link
Owner

sladg commented Feb 27, 2023

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.

  • I have server example.com on GoDaddy,
  • I want to use app.example.com on AWS.
    So I need to create new hosted zone app.example.com and on GoDaddy's end, I need to set NS records to use AWS's resolved.

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.

@sladg sladg added the question Further information is requested label Feb 27, 2023
@pinarruiz
Copy link
Author

The use case would be, for example having example.com on Cloudflare for example, and lets say that I want to deploy the nextjs site to app.example.com, not to example.com, i could set up a custom domain name on Cloudfront and also set a cname record at Cloudflare that is pointed at the cloudfront dristribution url (for example d111111abcdef8.cloudfront.net), so I would not need R53 records.

The whole thing would llok something like this:

  • Cloudfront: Distribution Url: d111111abcdef8.cloudfront.net, Alternate Domain: app.example.com
  • Cloudflare: app.example.com --(CNAME)--> d111111abcdef8.cloudfront.net

@sladg
Copy link
Owner

sladg commented Feb 27, 2023

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.

@sladg sladg closed this as completed Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants