Document history for Classic Load Balancers
The following table describes the releases for Classic Load Balancers.
| Change | Description | Date |
|---|---|---|
Desync mitigation mode | Added support for desync mitigation mode. For more information, see Configure desync mitigation mode for your Classic Load Balancer. | August 17, 2020 |
Classic Load Balancers | With the introduction of Application Load Balancers and Network Load Balancers, load balancers created with
the 2016-06-01 API are now known as Classic Load Balancers. For more
information about the differences between these types of load balancers,
see Elastic Load Balancing features | August 11, 2016 |
Support for AWS Certificate Manager (ACM) | You can request an SSL/TLS certificate from ACM and deploy it to your load balancer. For more information, see SSL/TLS certificates for Classic Load Balancers. | January 21, 2016 |
Support for additional ports | Load balancers can listen on any port in the range 1-65535. For more information, see Listeners for your Classic Load Balancer. | September 15, 2015 |
Additional fields for access log entries | Added the | May 18, 2015 |
Support for tagging your load balancer | Starting with this release, Elastic Load Balancing CLI (ELB CLI) has been replaced by AWS Command Line Interface (AWS CLI), a unified tool to manage multiple AWS services. New features released after ELB CLI version 1.0.35.0 (dated 7/24/14) will be included in the AWS CLI only. If you are currently using the ELB CLI, we recommend that you start using the AWS CLI instead. For more information, see the AWS Command Line Interface User Guide. | August 11, 2014 |
Idle connection timeout | You can configure the idle connection timeout for your load balancer. | July 24, 2014 |
Support for granting users and groups access to specific load balancers or API actions | You can create a policy to grant users and groups access to specific load balancers or API actions. | May 12, 2014 |
Support for AWS CloudTrail | You can use CloudTrail to capture API calls made by or on behalf of your AWS account using the ELB API, the AWS Management Console, the ELB CLI, or the AWS CLI. For more information, see Logging API calls for your Classic Load Balancer using AWS CloudTrail. | April 4, 2014 |
Connection draining | Added information about connection draining. With this support you can enable your load balancer to stop sending new requests to the registered instance when the instance is de-registering or when the instance becomes unhealthy, while keeping the existing connections open. For more information, see Configure connection draining for your Classic Load Balancer. | March 20, 2014 |
Access logs | You can enable your load balancer to capture detailed information about the requests sent to your load balancer and store it in an Amazon S3 bucket. For more information, see Access logs for your Classic Load Balancer. | March 6, 2014 |
Support for TLSv1.1-1.2 | Added information about TLSv1.1-1.2 protocol support for load balancers configured with HTTPS/SSL listeners. With this support, Elastic Load Balancing also updates the predefined SSL negotiation configurations. For information about the updated predefined SSL negotiation configurations, see SSL negotiation configurations for Classic Load Balancers. For information about updating your current SSL negotiation configuration, see Update the SSL negotiation configuration of your Classic Load Balancer. | February 19, 2014 |
Cross-zone load balancing | Added information about enabling cross-zone load balancing for your load balancer. For more information, see Configure cross-zone load balancing for your Classic Load Balancer. | November 6, 2013 |
Additional CloudWatch Metrics | Added information about the additional Cloudwatch metrics reported by Elastic Load Balancing. For more information, see CloudWatch metrics for your Classic Load Balancer. | October 28, 2013 |
Support for proxy protocol | Added information about proxy protocol support for load balancers configured for TCP/SSL connections. For more information, see Proxy protocol header. | July 30, 2013 |
Support for DNS failover | Added information about configuring Amazon Route 53 DNS failover for load balancers. For more information, see Using Amazon Route 53 DNS failover for your load balancer. | June 3, 2013 |
Console support for viewing CloudWatch metrics and creating alarms | Added information about viewing CloudWatch metrics and creating alarms for a specified load balancer using the console. For more information, see CloudWatch metrics for your Classic Load Balancer. | March 28, 2013 |
Support for registering EC2 instances in a default VPC | Added support for EC2 instances launched in a default VPC. | March 11, 2013 |
Internal load balancers | With this release, a load balancer in a virtual private cloud (VPC) can be made either internal or internet-facing. An internal load balancer has a publicly resolvable DNS name that resolves to private IP addresses. An internet-facing load balancer has a publicly resolvable DNS name that resolves to public IP addresses. For more information, see Create an internal Classic Load Balancer. | June 10, 2012 |
Console support for managing listeners, cipher settings, and SSL certificates | For information, see Configure an HTTPS listener for your Classic Load Balancer and Replace the SSL certificate for your Classic Load Balancer. | May 18, 2012 |
Support for Elastic Load Balancing in Amazon VPC | Added support for creating a load balancer in a virtual private cloud (VPC). | November 21, 2011 |
Amazon CloudWatch | You can monitor your load balancer using CloudWatch. For more information, see CloudWatch metrics for your Classic Load Balancer. | October 17, 2011 |
Additional security features | You can configure SSL ciphers, back-end SSL, and back-end server authentication. For more information, see Create a Classic Load Balancer with an HTTPS listener. | August 30, 2011 |
Zone apex domain name | For more information, see Configure a custom domain name for your Classic Load Balancer. | May 24, 2011 |
Support for X-Forwarded-Proto and X-Forwarded-Port headers | The X-Forwarded-Proto header indicates the protocol of the originating request, and the X-Forwarded-Port header indicates the port of the originating request. The addition of these headers to requests enables customers to determine if an incoming request to their load balancer is encrypted, and the specific port on the load balancer that the request was received on. For more information, see HTTP headers and Classic Load Balancers. | October 27, 2010 |
Support for HTTPS | With this release, you can leverage the SSL/TLS protocol for encrypting traffic and offload SSL processing from the application instance to the load balancer. This feature also provides centralized management of SSL server certificates at the load balancer, rather than managing certificates on individual application instances. | October 14, 2010 |
Support for AWS Identity and Access Management (IAM) | Added support for IAM. | September 2, 2010 |
Sticky sessions | For more information, see Configure sticky sessions for your Classic Load Balancer. | April 7, 2010 |
AWS SDK for Java | Added support for the SDK for Java. | March 22, 2010 |
AWS SDK for .NET | Added support for the AWS SDK for .NET. | November 11, 2009 |
New service | Initial public beta release of Elastic Load Balancing. | May 18, 2009 |
