One of the ways you can prevent a server from becoming overloaded is to use the Connection Throttling feature of Cloud Load Balancers. Connection throttling basically imposes limits on the number of connections per IP address. This feature helps prevent malicious or abusive traffic to your server and its installed applications.
Note: This procedure assumes you're working with an existing load balancer. If you don't have a load balancer yet, create one now using these instructions: Configuring a Load Balancer.
To configure connection throttling:
The following pop-over appears:

When configuring connection throttling, you can specify the following options:
Specifies the maximum number of simultaneous connections to allow from a single IP address. You can specify a value between 1 and 100000.
Specifies the level of simultaneous connections from any IP address at which to apply the throttling restrictions defined by the Limit to and Timeframe fields (see below). You can specify a value between 1 and 1000.
Specifies the maximum number of new connections allowed from a single IP address in the defined Timeframe (see Timeframe below). Specify a value between 1 and 100000.
Specifies the interval (in seconds) at which the limit for new connections is assessed once the Threshold is reached. Specify a value between 1 and 3600.
The following field is updated automatically based on your settings for the Threshold, Limit to, and Timeframe fields:
Describes the results that will be produced by your settings for Threshold, Limit to, and Timeframe.
For example, if you enter 25 simultaneous connections from any IP for the Threshold, 25 new connections for Limit to, and 5 seconds for the Timeframe, after 25 simultaneous connections from any IP, your load balancer would only allow a maximum of 25 new connections for a single IP address every 5 seconds.
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License

7 Comments
Inconsistent explanation
Re: image
Sorry Jered, I was not
If you read the config options that appear in the image you'll see that the explanation below happens to be for other terms options. The image seems to be the real deal, and the explanation obsolete.
re: screenshot
Inconsistent Explanation
We've updated this article so that the labels in explanation match the labels in the UI. Thanks for bringing this to our attention!
Would be good to explain what exactly happens when throttling
Hi Nate,
When connection throttling is configured on a load balancer, the load balancer will limit the number of connections from each client (unique IP) to the VIP. This does not impact connections from the LB to the nodes on the backend. Using the example given above, each unique client IP is only permitted 100 concurrent connections to the VIP. When a client reaches 25 concurrent connections, the LB will allow the client to initiate 25 more connections after 5 seconds. This pattern will repeat until 100 connections are reached. Once the limit of 100 concurrent sessions is reached and the client attempts to initiate the 101st session, the LB will respond to that client with a 502 for that session.
Regards,
Add new comment