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

Deploy to target already existing cloudfront #18

Open
2 tasks done
hanseungyoo opened this issue Dec 1, 2023 · 1 comment
Open
2 tasks done

Deploy to target already existing cloudfront #18

hanseungyoo opened this issue Dec 1, 2023 · 1 comment

Comments

@hanseungyoo
Copy link

What is the problem this feature will solve?

I am already running cloudfront in our production environment and our domain is connected.
When creating a new cloudfront distribution and connecting the domain, it takes time to complete the connection, so I wish I could connect to the existing cloudfront instead of creating a new cloudfront distribution.

What is the feature that you are proposing to solve the problem?

I wish there was a feature that could deploy to an existing Cloudfront ID as a target.

What alternatives have you considered?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Sensitive Information Declaration

  • I confirm that neither PII/PID nor sensitive data are included in this form
@Tomdango
Copy link
Collaborator

This would certainly be possible. The Cloudfront module only outputs the aws_cloudfront_distribution and aws_wafv2_web_acl resource, and these could be passed in as variables and a flag created to skip the Cloudfront module.

The Cloudfront module is integral to the function of the module, so a warning here that bringing your own resources would come at your own risk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants