2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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
beantwortet vor 2 Monaten
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.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 9 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
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