Release: Elastic Load Balancing on 2011-08-30
Release: Elastic Load Balancing on 2011-08-30
This release provides support for configurable cipher sets, secure communication from the corresponding Elastic Load Balancer to application servers, health checks for back-end servers using HTTPS, back-end server authentication, and a new API version: 2011-08-15.
| Release Date: | 08/30/2011 |
|---|---|
| Latest API Version: | 2011-08-15 |
| Latest WSDL: | View WSDL |
New Features
| Feature | Description |
|---|---|
| Configurable cipher support | You can now select a pre-defined set of ciphers or specify your own list of ciphers to use for SSL termination at the Elastic Load Balancer. NOTE: The AWS Management Console currently supports specifying a single cipher set for the Elastic Load Balancer, while the API and CLI tools provide full access to specify the ciphers on a per-listener basis. For more information, see Elastic Load Balancing Security Features. |
| Back-end SSL | Application servers can now accept secure communication from the corresponding Elastic Load Balancer. NOTE: The AWS Management Console currently supports specifying a single certificate for all secure listeners, while the API and CLI tools provide full access to specify the certificate on a per-listener basis. For more information, see Elastic Load Balancing Security Features |
| Secure health checks | In cases where HTTPS is required for all traffic entering the back-end server, Elastic Load Balancing can now perform health checks using HTTPS. For more information, see How to Create a LoadBalancer. |
| Back-end server authentication | You can create a white list of public keys and associate them with your back-end servers. Elastic Load Balancing authenticates your back-end servers with the public keys in your white list and communicates only with back-end servers that pass this authentication check. For more information, see Elastic Load Balancing Security Features |
Other Changes
| Change | Description |
|---|---|
| API version deprecation | With this release, we are also announcing plans to deprecate the 2009-05-15 and 2009-11-25 API versions in 18 months, on February 28, 2013. |
