You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
Sensitive Information Declaration
The text was updated successfully, but these errors were encountered: