Wondering how to fix Cloudfront error : The request could not be satisfied? We can help you!
Here at Bobcares, we fix similar Cloudfront errors for our customers as a part of our Server Management Services.
Today let’s see how our Support Engineers do this for our customers.
How to troubleshoot Cloudfront error : The request could not be satisfied
Generally, this error can occurs due to AWS Web Application Firewall (AWS WAF) rules associated with the CloudFront distribution.
Following are the steps that our support engineers follow to troubleshoot this error.
If the default action is set to Allow
When the default action is set to Allow, the request that returns the “Request Blocked” error will likely match a rule that has Action set to Block.
To resolve the error when the default action is Allow, we can use the following steps:
1. We can review requests and ensure that they don’t match the conditions for any AWS WAF rules with Action set to Block.
2. If valid requests match the conditions for a rule that blocks requests we must update the rule to allow the requests.
If the default action is set to Block
When the default action is set to Block, AWS WAF blocks requests in the following scenarios:
- The request matches the conditions of a rule that has Action set to Block.
- And when the request doesn’t match the conditions of any rule that has Action set to Allow.
To resolve the error when the default action is Block we can use the following steps:
1. We can review requests and ensure that they match the conditions for any AWS WAF rules with Action set to Allow.
2. If valid requests don’t match any existing rules that allow requests we can create a rule that allows the requests.
[Need assistance? We can help you]
Conclusion
To conclude, we saw the steps that our Support Techs follow to fix this Cloudfront error for our customers.
0 Comments