WAF & Edge Security across clouds
Web application firewalls and edge request filtering - managed rule sets, rate limits and IP controls in front of your origin.
3 verified modules, 2 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| Akamai | Akamai App & API Protector (WAF) | static-validated |
| AWS | WAFv2 Web ACL (managed rules + rate limit) | ✓ live-tested |
| Google Cloud | Cloud Armor Security Policy (WAF) | ✓ live-tested |
How to choose
Put it where your traffic already terminates: if you front the site with a CDN, use that vendor WAF rather than standing up a second edge for requests to pass through. Then check whether you get maintained managed rule groups or only rules you write and own forever.
When not to use
A WAF is a filter, not a fix. It buys time against a known shape of request; the vulnerability underneath is still there, and a rule tuned to block it will also block someone legitimate eventually.
Other solutions
Managed Relational Database18Managed Kubernetes15Virtual Machines13Messaging & Pub/Sub11Load Balancer10DNS & Traffic Management10Virtual Private Cloud (VPC)9Serverless Containers7Secrets & Key Management7Serverless Functions6Object Storage5API Gateway5Identity & Access5Container Registry3CDN & Edge Delivery3In-Memory Cache3Monitoring & Observability3Shared File Storage3