Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

AWS CloudFront “The request could not be satisfied”

by | Oct 20, 2021

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:

  1. The request initiates over HTTP, but the CloudFront distribution allows only HTTPS requests.
  2. 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:

  1. Initially, we open the Amazon CloudFront console.
  2. Then we select the distribution that is returning the Bad Request error.
  3. After that, we select the Behaviors view where we can select the behavior that matches the request.
  4. Then, select Edit.
  5. For Viewer Protocol Policy, we select either HTTP and HTTPS or Redirect HTTP to HTTPS.
  6. Eventually, we click Yes, Edit.

On the other hand, to associate an alternate domain name (CNAME) with a distribution, we follow these steps:

  1. First, we open the Amazon CloudFront console.
  2. Then we select the distribution that returns the Bad Request error.
  3. After that, we select the General view > Edit.
  4. For Alternate Domain Names (CNAMEs), we enter the CNAME that we want to associate with the CloudFront distribution.
  5. Finally, we select Yes, Edit.

[Need further assistance? We are glad to assist]

 

Conclusion

In short, we saw how our Support Techs fix the CloudFront error for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF