2 Answers
- Newest
- Most votes
- Most comments
1
There could be multiple reasons.
Did you check your content is available in S3 ? ( if thats the origin ? ). Any policy/permission change on s3 ? ( in that the origin? ).
Next step would be have a look at this documentation to correlate the issue.
You may need to enable cloudfront logs to dig deep into actual error code. https://docs.aws.amazon.com/athena/latest/ug/cloudfront-logs.html
answered 2 months ago
1
My hunch would be something behind your api gateway is throwing the 500 errors.
I would look at your application logs and like Muhammad said enable cloudfront logs.
Relevant content
- asked a year ago
- Accepted Answerasked 9 months ago
- Accepted Answerasked 2 years ago
- CloudFront - One or more of the CNAMEs you provided are already associated with a different resourceAccepted Answerasked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 months ago
Hello,
Unfortunately, I have tried all the options you mentioned. I have several types of endpoints for my CloudFront distributions, like API gateway, S3 buckets and others...
...and I keep getting these messages every 1-2 days