ERROR: The request could not be satisfied
1 min readJul 22, 2021
Ever received this error while calling an APIGateway endpoint? Well I did and spent 3 hours trying to figure out what was happening. It didn’t help I started getting this during a wide DNS outage.
Long story short, APIGateway allows you to specify a request body model on a GET request, however, CloudFlare, which I guess APIGateway uses even if you don’t configure it, will reject the request. Leaving you with this response
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"><TITLE>ERROR: The request could not be satisfied</TITLE></HEAD><BODY><H1>403 ERROR</H1><H2>The request could not be satisfied.</H2><HR noshade size="1px">Bad request.We can't connect to the server for this app or website at this time. There might be too much traffic or aconfiguration error. Try again later, or contact the app or website owner.<BR clear="all">If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.<BR clear="all"><HR noshade size="1px"><PRE>Generated by cloudfront (CloudFront)Request ID: <redacted></PRE><ADDRESS></ADDRESS></BODY></HTML>
Fun times.
