2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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
답변함 2달 전
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.
관련 콘텐츠
- AWS 공식업데이트됨 2년 전
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