-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: CloudFront distribution with an invalid OAC waits for deployment without creating the distribution #26850
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Thanks dear i am finding the solution from last week, finally today you solve my problem |
how can i make a public and private key for cloud front to restrict viewer policy |
I just ran into this issue... somewhat. I have the configuration you give in your example. I'm greeted with this error upon
I think this bug is fixed. |
Error: updating CloudFront Distribution (XXXXXXXXXX): IllegalOriginAccessConfiguration: Illegal configuration: The origin type and OAC origin type differ. |
Can someone please help for above error am getting while using custom_origin_config |
You can't use
See this for more info: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html |
After removing custom_origin_config block it's giving me below error :
|
I want to set below origin block for my cloudfront distribution as I want to use website_endpoint as a domain name for cloudfront distribution.
|
This thread is not the right place to debug this. Let's please keep the discussion on topic. For your issue, see the link I gave you. You don't use the S3 website links in CloudFront when using OAC. |
If S3 website link is not allowed in OAC then what needs to be done to use S3 website link in cloudfront distribution ? |
👋 for anyone seeing this... here's an mvp cloudfront/s3 OAC working example 👉 https://gist.github.com/chrispsheehan/ed9de23b4b36ca890082ae56e6ab7455 I found some conflation between the (legacy) OAI and (currently recommended) OAC approaches gave me errors |
so there's no way to deploy an S3 static website behind Cloudfront with terraform? |
Terraform Core Version
1.1.8
AWS Provider Version
4.31.0
Affected Resource(s)
Expected Behavior
When the
origin_access_control_origin_type
does not match the origin type, Terraform should report an error.Actual Behavior
terraform apply
saysStill creating...
but the Console shows no Distribution is being deployed.Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform init
terraform apply
Debug Output
debug.log
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No response
The text was updated successfully, but these errors were encountered: