Enforce Cloud Armor metadata rate-limit rule - #3762
Merged
Merged
Conversation
metadata (30/60s) enforced 2026-07-21: worst legit per-IP rate observed in the preview window was 5/min, 6x under the threshold. calculate (75/60s) stays in preview — observed legit/partner clients run 39-88/min there, so enforcing would 429 real use including the partner's API fallback. Also documents that Armor throttle rules log only CONFORM in preview, so enforcement readiness must be judged from raw LB-log rate analysis. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3762 +/- ##
==========================================
+ Coverage 80.03% 85.49% +5.46%
==========================================
Files 70 95 +25
Lines 4342 5902 +1560
Branches 809 1032 +223
==========================================
+ Hits 3475 5046 +1571
+ Misses 648 559 -89
- Partials 219 297 +78 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/{cc}/metadataper-IP throttle (30/60s) onpol-api-lb— removes preview. Worst legitimate per-IP rate in the preview window was 5/min (6× headroom); the rule's target is overnight scraper waves./{cc}/calculate(-full)throttle (75/60s) in preview: observed legitimate/partner clients run 39–88/min on that path, so enforcing would 429 real use — including a partner's documented "fall back to the internal API when household API latency > 30s" behavior.docs/migration/armor/and documents that Cloud Armor throttle rules only logCONFORMin preview (so enforcement readiness is judged from raw LB-log rate analysis, not preview outcome counts).pol-api-lbpolicy on 2026-08-30. The refreshed snapshot is byte-for-byte identical to the 2026-07-21 enforced-policy snapshot, confirming that the deployed configuration has not drifted.Verified: normal (gzip) metadata fetches return 200 post-enforcement; rule state confirmed via
security-policies describe(1000 preview=false, 1100 preview=true); current deployed policy re-exported and compared with the prior snapshot.🤖 Generated with Claude Code