Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not sure if it GCP does, but the load balancer can handle HTTPS termination and even filter out DOS attacks or handle rate limiting.


Hi searchfaster,

Can you elaborate more from documentation that this new features can filter out DDOS attacks or handle rate limiting? Because i can't find out that statement

Thank you


Google's load balancers are global - as in they will route requests to the nearest region to the user without you having to run separate load balancers in each with dns routing.

The backend services hooked up to the load balancer can have healthchecks and capacity limits based on req/sec or CPU usage, so a region that's close by but overloaded will be skipped for a further region that has available capacity.

GCP also absorbs layer 4 and below attacks automatically. https://cloud.google.com/files/GCPDDoSprotection-04122016.pd...


Hey dyngts, sorry I have not used GCP load balancers extensively and was not sure if this is supported.

Manigandham's post below confirms it though with all the necessary information.


http(s) load balancer only route http(s) requests to your compute instances, and hide the instance IPs. So at least Layer 3 DDOS can not touch your instances.


But, when talking Kubernetes. it is currently no support for internal load balancer, right? so it's still have vulnerability to get exposed to the world. Any comment about this?

Thank you!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: