How do I resolve the "403 ERROR - The request could not be satisfied. Bad Request" error in CloudFront?

2 minute read

I want to troubleshoot the Amazon CloudFront "403 ERROR - The request could not be satisfied. Bad Request" error.

Short description

You might receive the "403 ERROR - The request could not be satisfied. Bad Request" error message for the following issues:

The request is initiated over HTTP, but the CloudFront distribution allows only HTTPS requests.
The requested alternate domain name (CNAME) isn't associated with the CloudFront distribution.

Note: If you own an application or website that uses CloudFront to serve content to end users, complete the troubleshooting steps for your error. If you receive this error when you view an application or access a website, then contact the provider or website owner for assistance.

Resolution

Allow HTTP requests

Complete the following steps:

Open the CloudFront console.
Select the distribution that returns the "Bad Request" error.
Choose the Behaviors tab, and then choose the behavior that matches the request. Then, choose Edit.
For Viewer Protocol Policy, choose either HTTP and HTTPS or Redirect HTTP to HTTPS.
Note: HTTP and HTTPS allows connections on both HTTP and HTTPS. Redirect HTTP to HTTPS automatically redirects HTTP requests to HTTPS.
Choose Save Changes.

Associate a CNAME with a distribution

Complete the following steps:

Open the CloudFront console.
Select the distribution that returns the "Bad Request" error.
Choose the General tab.
Under Settings, choose Edit.
For Alternate Domain Names (CNAMEs), choose Add Item.
Enter the CNAME that you want to associate with the CloudFront distribution.
Under Custom SSL certificate, choose the certificate that covers the domain.
Note: An SSL certificate is required to associate a CNAME with a distribution. For more information see, Requirements for using alternate domain names.
Choose Save changes.