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
Created a bucket without a website, to then realise I need a website bucket to load index.html for 'folder' like URLs ending with /. CloudFront should use the website origin that will do the web serving.
All I did was, added website_enabled = true to my config.
Got this error:
321: resource "aws_cloudfront_distribution" "default" {
The argument "origin.0.domain_name" is required, but no definition was found.
Origin bucket deleted, new bucket with website name created with no error.
Everything else (CloudFront distribution, SSL certificate) should stay intact.
Steps to Reproduce
Steps to reproduce the behavior:
Add website_enabled = true
Run terraform plan
See error
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
OS: macOS 10.15.7
Terraform version: v0.13.5
The text was updated successfully, but these errors were encountered:
By destroying the whole module (all resources created by this module) using the terraform destroy command and re-creating everything from scratch worked.
But it's not ideal, we should avoid the need of using terraform destroy.
Describe the Bug
index.html
for 'folder' like URLs ending with/
. CloudFront should use the website origin that will do the web serving.website_enabled = true
to my config.I think it's because of some circular dependency.
By setting
website_enabled = true
:true
: https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/blob/master/main.tf#L8new
: https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/blob/master/main.tf#L30Expected Behavior
Origin bucket deleted, new bucket with website name created with no error.
Everything else (CloudFront distribution, SSL certificate) should stay intact.
Steps to Reproduce
Steps to reproduce the behavior:
website_enabled = true
terraform plan
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
The text was updated successfully, but these errors were encountered: