AWS Firewall Manager Integration: AWS Firewall Manager allows you to remotely create and maintain web application deployments over different AWS accounts.This enables businesses to instantly establish and manage rules, as well as include these into the design and development processes. Full Feature API: It may be managed entirely using APIs.Real-time Visibility: It collects raw requests and offers real-time analytics, including IPs, geolocations, URIs, User-Agent, and Relevant individuals.But when I turn on the Cloudflare proxy I get an error as described here: To proxy or not to proxy.The following are the features of the AWS Web Application Firewall. This did work as long as I configured the CNAME in Cloudflare as ‘DNS-only’ (even in SSL(Strict) mode). I replaced the Cloudflare origin certificate by a certificate created through ACM and updated the config in API Gateway. So I followed the advice from user ‘Judge’ in this thread: Can't get certificate chain This seems to be due to the fact that AWS no longer accepts Cloudflare’s self-signed certificates.

Unfortunately this didn’t work, and I got an error when I tried calling my API. I also generated a Cloudflare origin certificate and imported it into AWS Certificate Manager (adding the Cloudflare CA certificate to the chain), and then associated it to a Custom Domain Name in API Gateway, added the mapping and updated the CNAME record in Cloudflare DNS to point my subdomain to the new API Gateway endpoint. I’m trying to set up a Cloudflare proxy for AWS API Gateway but I’m struggling with the configuration.

Aws api gateway waf