When HTML pages are updated, I programmatically request invalidations from AWS Cloudfront.
Occasionally, the invalidation request takes a number of seconds, and gives an error, reading (in part)
Server error: `POST https://cloudfront.amazonaws.com/2020-05-31/distribution/(mydistribution)/invalidation` resulted in a `503 Service Unavailable` response:\n<?xml version="1.0"?>\n<ErrorResponse xmlns="http://cloudfront.amazonaws.com/doc/2020-05-31/"><Error><Type>Receiver</Type (truncated...)\n ServiceUnavailable (server): CloudFront encountered an internal error. Please try again. - <?xml version="1.0"?>\n<ErrorResponse xmlns="http://cloudfront.amazonaws.com/doc/2020-05-31/"><Error><Type>Receiver</Type><Code>ServiceUnavailable</Code><Message>CloudFront encountered an internal error. Please try again.</Message></Error><RequestId>(myrequestid)</RequestId></ErrorResponse>
This seems to be an internal error from AWS Cloudfront, and it appears to be happening more recently. The AWS Cloudfront documents do not mention this error, nor how to handle it.
The origin server is responsive and does not show any additional errors when an invalidation is being requested. It does not seem to be under heavy load.
I think this is a bug with Cloudfront; but I have no paid support in order to report it. What should my next steps be?
AWS公式更新しました 2年前
Thanks. Paying to access support to report a bug to AWS staff seems sub-optimal...
Is it a bug? Don't know. Could be. Might not be. Could be some other cause. Without knowing the account number, request identifiers, times, dates and all that other information there's no way to say. Hence my encouragement to engage with the support team.