Skip to content
Notifications
Clear all

ELI5: The difference between Prolexic and Kona Site Defender.

3 Posts
3 Users
0 Reactions
64 Views
(@miked)
Eminent Member
Joined: 4 months ago
Posts: 12
Topic starter   [#4639]

They're both Akamai DDoS products but for different network layers. The confusion is intentional. Here's the split:

* **Prolexic**: Protects your **network infrastructure** (IP addresses). It's for scrubbing attacks against your data center, cloud VPC, or any publicly routable IP. Think volumetric floods (UDP, SYN) and protocol attacks.
* **Kona Site Defender**: Protects your **web applications** (HTTP/HTTPS traffic). It sits in front of your web servers to stop layer 7 attacks like HTTP floods, slowloris, or bot-driven abuse.

Simple rule:
* Getting flooded off the internet? Your routers are down? That's a **Prolexic** problem.
* Your website is slow or returning 503s, but the server is reachable? That's a **Kona** problem.

You often need both. Prolexic cleans the pipe, Kona secures the application at the other end.

Example config mindset:
```
# Prolexic: Your BGP session or DNS points to their scrubbing centers.
# Kona: Your web traffic routes through their edge, with rulesets for apps.
```

-miked


Numbers don't lie


   
Quote
(@benchmark_basher)
Reputable Member
Joined: 6 months ago
Posts: 312
 

Good high-level split, but the real-world overlap is where it gets messy. Akamai's own docs push you to "Prolexic with Kona" for any serious deployment, so that "simple rule" falls apart fast.

I ran tests a few years back. A sustained HTTP flood at moderate volume triggered Kona mitigations. Crank it up to saturate the pipe, and Prolexic kicked in first, even though it was layer 7 traffic. The handoff isn't always clean.

Your config example is spot on. Just don't think you can pick one and be done unless your attack surface is trivial.


-- bb


   
ReplyQuote
(@cloud_cost_analyst_pro)
Honorable Member
Joined: 8 months ago
Posts: 469
 

Good practical split. The cost implication is what matters.

Your rule of thumb works for initial triage, but the billing models force the decision. Prolexic is often IP/commitment based. Kona is request/GB based. A "Kona problem" hitting volumetric scale becomes a Prolexic bill.

You need both, but you size them based on where your spend breaks. Layer 3 floods are cheaper to scrub at Prolexic scale. Letting them hit Kona's pricing will wreck your budget.


cost per transaction is the only metric


   
ReplyQuote