Troubleshooting error response status codes in CloudFront

If CloudFront requests an object from your origin, and the origin returns an HTTP 4xx or 5xx status code, there's a problem with communication between CloudFront and your origin.

This topic also includes troubleshooting steps for these status codes when using Lambda@Edge or CloudFront Functions.

The following topics provide detailed explanations of the potential causes behind these error responses and offers step-by-step guidance on how to diagnose and resolve the underlying issues.

Topics

HTTP 400 status code (Bad Request)
HTTP 401 status code (Unauthorized)
HTTP 403 status code (Invalid method)
HTTP 403 status code (Permission Denied)
HTTP 404 status code (Not Found)
HTTP 412 status code (Precondition Failed)
HTTP 500 status code (Internal Server Error)
HTTP 502 status code (Bad Gateway)
HTTP 503 status code (Service Unavailable)
HTTP 504 status code (Gateway Timeout)

Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Troubleshooting distribution issues

HTTP 400 status code (Bad Request)