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

feat: Possibility to use custom domain name with Cloudfront #416

Merged
merged 2 commits into from
Mar 15, 2024

Conversation

JeromeGuyon
Copy link
Contributor

Issue #298: Possibility to use custom domain name with Cloudfront

Description of changes:

  • add possibility to configure a custom domain for the public cloudfront
  • add corresponding documentation

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

},
},
{
type: "input",
name: "domain",
message: "Domain for private website",
message(): string {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about asking for Route53 Zone Id too so we can create the A record with CDK directly?

Copy link
Contributor Author

@JeromeGuyon JeromeGuyon Mar 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good point.
Most of the time Route53 public zone is centralized in an AWS Account.
This does not limits this possibility (local or central).

I propose to create another PR for this,
Domain Names and Certificates
with a migration from CloudFrontWebDistribution API

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed

@bigadsoleiman bigadsoleiman merged commit 9ccf06e into aws-samples:main Mar 15, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants