Cloud Armor returns 403 Forbidden: request blocked by a security policy rule
A Cloud Armor policy on the load balancer denied the request (IP, geo, preconfigured WAF rule or rate limit).
Cloud Armor 403 ForbiddenenforcedSecurityPolicy outcome DENYCloud Armor blocked request preconfigured WAFsecurity policy deny 403 load balancerCloud Armor rate limit exceeded 429 Meaning
Find the matching rule in the load balancer's request logs (enforcedSecurityPolicy), then tune the rule: add an allow rule with lower priority number for trusted IPs, switch a WAF rule to preview mode, exclude false-positive signatures, or adjust rate limits.
Common causes
- Preconfigured WAF rule false positive (SQLi/XSS)
- Geo/IP deny rule
- Rate-based ban
- Rule priority order wrong
- Missing allow rule for health checks/partners
⚡ Quick fix
- Check
enforcedSecurityPolicy.nameandoutcomein logs - Put allow rules at a lower priority number
- Use preview mode and exclusions for WAF rules
Detailed fix by platform
Shell
gcloud logging read 'resource.type="http_load_balancer" AND jsonPayload.enforcedSecurityPolicy.outcome="DENY"' --limit=5
How to diagnose
- Rule — Which matched?
- Priority — Correct?
- Mode — Preview first?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026