r/aws
๐ [AWS Firewall Manager] Large-Scale Deployment Experiences & False Positive Management
- upvotes
- 4
- comments
- 1
Post
Highlighted: the lines this signal was extracted from
Hi r/aws, Weโre planning to deploy AWS Firewall Manager (FMS) with WAFv2 across an AWS organization with 334 active accounts, including: 725 CloudFront distributions, 44 public ALBs and 12 public API Gateway stages, 431 attached Web ACLs (157 in production). Our goal is to centralize a common baseline (IP blacklist, geoblocking, AWS Managed Rules) while preserving user-managed application-specific rules (allowlists, rate limits, CAPTCHA, etc.). ๐ Questions for the Community: Implementation Mode: Did you use RETROFIT_EXISTING (injecting the baseline into existing Web ACLs) or a full replacement of ACLs? โ Weโre leaning toward RETROFIT_EXISTING to preserve user-managed rules, but weโre concerned about temporary rule duplication (e.g., F5/Fortinet rules existing both locally and centrally). Phased Migration: How did you structure your migration (by resource type, environment, etc.)? How did you handle exceptions (e.g., accounts with different IP profiles like X-Forwarded-For vs. origin)? Marketplace Rules (F5/Fortinet) Management: Did you centralize F5/Fortinet via FMS, or did you leave them under user control? โ We want to centralize F5 for APIs and Fortinet for ALBs, but weโre particularly concerned about false positives (e.g., a specific F5 rule causing issues for a particular account). How did you ensure these didnโt disrupt legitimate traffic? ๐ก Key...
Keep reading with a free account
The rest of this post, and every signal for F5, is in your free account.
Also quoted as evidence
๐ก Key Concerns: Avoiding false positives (e.g., ensuring a specific F5 rule doesnโt block legitimate traffic for a particular account). Rule coexistence (e.g., temporary duplication of F5/Fortinet rules during migration).
From the post