AWS CloudFront returns “The request could not be satisfied” due to majorly two reasons.
Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.
Today, let us discuss the reasons and how we can fix them.
AWS CloudFront “The request could not be satisfied”
Most often, the error message states:
“The request could not be satisfied. Bad Request.”
Our Support Techs recommend using this troubleshooting method if we own the application or website that uses CloudFront to serve content to end-users.
However, if we come across this error while trying to view an application or access a website, we have to contact the provider or website owner for assistance.
The error message for the client can occur due to one of the following reasons:
- The request initiates over HTTP, but the CloudFront distribution allows only HTTPS requests.
- The requested alternate domain name (CNAME) does not associate with the CloudFront distribution.
Moving ahead, let us see how our Support Techs perform the resolution.
In order to allow HTTP requests, we follow these steps:
- Initially, we open the Amazon CloudFront console.
- Then we select the distribution that is returning the Bad Request error.
- After that, we select the Behaviors view where we can select the behavior that matches the request.
- Then, select Edit.
- For Viewer Protocol Policy, we select either HTTP and HTTPS or Redirect HTTP to HTTPS.
- Eventually, we click Yes, Edit.
On the other hand, to associate an alternate domain name (CNAME) with a distribution, we follow these steps:
- First, we open the Amazon CloudFront console.
- Then we select the distribution that returns the Bad Request error.
- After that, we select the General view > Edit.
- For Alternate Domain Names (CNAMEs), we enter the CNAME that we want to associate with the CloudFront distribution.
- Finally, we select Yes, Edit.
[Need further assistance? We are glad to assist]
In short, we saw how our Support Techs fix the CloudFront error for our customers.