-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
AWS Cloudfront doesn't support ALB site as an Origin #10572
Comments
If anyone else got this error: when trying to use S3 website as origin (if index document functions of S3 are required) the custom_origin_config is needed:
... not sure if this is a bug. |
I'm experiencing the same issue. @Stephan1984 suggests to use |
The custom_origin_config is required because terraform will insist that the bucket name is incorrect as it doesn't follow the irlpodcast.s3.amazonaws.com format. requires terraform 0.9.8 see also: hashicorp/terraform#10572 hashicorp/terraform#13627
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Hello everyone
On document said terraform support S3 or Website be a Origin, but I try many time get same error is: The parameter Origin DomainName does not refer to a valid S3 bucket
Here's my cloudfront.tf
and I got this error below:
`Error applying plan:
1 error(s) occurred:
status code: 400, request id: 242113c0-bc4d-11e6-afa0-5da45ee7023c
`
The text was updated successfully, but these errors were encountered: