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年前
- AWS公式更新しました 2年前
- AWS公式更新しました 1年前
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