Configure your Classic Load Balancer
After you create a Classic Load Balancer, you can change its configuration. For example, you can update the load balancer attributes, subnets, and security groups.
Load balancer attributes
- Connection draining
-
If enabled, the load balancer allows existing requests to complete before the load balancer shifts traffic away from a deregistered or unhealthy instance.
- Cross-zone load balancing
-
If enabled, the load balancer routes the request traffic evenly across all instances regardless of the Availability Zones.
- Desync migitation mode
-
Determines how the load balancer handles requests that might pose a security risk to your application. The possible values are
monitor,defensive, andstrictest. The default isdefensive. - Idle timeout
-
If enabled, the load balancer allows the connections to remain idle (no data is sent over the connection) for the specified duration. The default is 60 seconds.
- Sticky sessions
-
Classic Load Balancers support both duration-based and application-based session stickiness.
Load balancer details
- Security groups
-
The security groups for your load balancer must allow traffic on the listener and health check ports.
- Subnets
-
You can expand the ability of your load balancer to additional subnets.
- Proxy protocol
-
If enabled, we add a header with connection information that is sent to the instance.
- Tags
-
You can add tags to categorize your load balancres.
