I recently setup WAF and POST upload requests (greater than ~10 GB, no issues for small files) are getting blocked.
413 is returned with the response shown below.
<!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>413 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 a configuration 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: XXXXXXXXXXXXX==
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>
The issue is I cannot find this request ID inside the WAF Logs. It looks like it is getting blocked before the waf rules, is that possible? I tried adding custom rules (with max priority) to pass everything through for this specific API but it's getting blocked even before it reaches there.
Any idea why this happens ?
Thanks
AWS OFFICIALAktualisiert vor 9 Monaten