Cloudfront invalidation request fails: "CloudFront encountered an internal error."


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` resulted in a `503 Service Unavailable` response:\n<?xml version="1.0"?>\n<ErrorResponse xmlns=""><Error><Type>Receiver</Type (truncated...)\n ServiceUnavailable (server): CloudFront encountered an internal error. Please try again. - <?xml version="1.0"?>\n<ErrorResponse xmlns=""><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?

asked 3 months ago64 views
2 Answers

I'd normally encourage you to raise a support case here; but as you point out you have no paid support.

Depending on the criticality of this issue I would consider paying for support in order to get assistance with this - from here (re:Post) there's not a lot that we can do with this issue; we're all volunteers and we have no visibility into user identity; accounts; services; etc.

profile picture
answered 3 months ago
  • 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.


As a step forward, I've reported this as an error in the Cloudfront documentation, since this error should be documented.

answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions