Configure error response behavior
You have several options to manage how CloudFront responds when there’s an error. To configure custom error responses, you can use the CloudFront console, the CloudFront API, or Amazon CloudFormation. Regardless of how you choose to update the configuration, consider the following tips and recommendations:
-
Save your custom error pages in a location that is accessible to CloudFront. We recommend that you store them in an Amazon S3 bucket, and that you don’t store them in the same place as the rest of your website or application’s content. If you store the custom error pages on the same origin as your website or application, and the origin starts to return 5xx errors, CloudFront can’t get the custom error pages because the origin server is unavailable. For more information, see Store objects and custom error pages in different locations.
-
Make sure that CloudFront has permission to get your custom error pages. If the custom error pages are stored in Amazon S3, the pages must be publicly accessible or you must configure a CloudFront origin access control (OAC). If the custom error pages are stored in a custom origin, the pages must be publicly accessible.
-
(Optional) Configure your origin to add a
Cache-ControlorExpiresheader along with the custom error pages, if you want. You can also use the Error Caching Minimum TTL setting to control how long CloudFront caches the custom error pages. For more information, see Control how long CloudFront caches errors.
Configure custom error responses
To configure custom error responses in the CloudFront console, you must have a CloudFront distribution. In the console, the configuration settings for custom error responses are only available for existing distributions. To learn how to create a distribution, see Get started with a basic CloudFront distribution.