Release: Elastic Load Balancing on 2009-05-18
New Features
This is the initial public beta release of Elastic Load Balancing. Please see the Elastic Load Balancing page at http://aws.amazon.com/elasticloadbalancing for details.
Known Issues
| Issue | Description | Impact |
|---|---|---|
| 1 | Elastic Load Balancing is a feature of Amazon Elastic Compute Cloud (EC2). | You must be signed up for Amazon Elastic Compute Cloud (EC2) service in order to call the Elastic Load Balancing APIs. |
| 2 | The Amazon CloudWatch Latency metric for a LoadBalancer aggregates the latency for all requests to all LoadBalancer ports (Listeners ) into a single metric. | If you have a LoadBalancer that is handling traffic on multiple ports, you cannot view the Latency of the requests on a per-port basis. Moreover, for LoadBalancers with TCP listeners, the Latency metric is not a meaningful measure of the TCP request latency. |
| 3 | When an Availability Zone is removed from the LoadBalancer, instances in that Availability Zone may continue to take traffic after they are described as OutOfService by DescribeInstanceHealth. | Instances may continue to take traffic for a short period after the Availability Zone is removed from the LoadBalancer. |
| 4 | A LoadBalancer might not fail traffic away from an Availability Zone if all the instances in a given Availability Zone fail health checks. | In the event that all your instances in an Availability Zone fail, traffic will still be routed to the failed Availability zone and those requests will fail. |
| 5 | When instances are registered with a LoadBalancer, they are assumed to be healthy. | Regardless of the actual health of an instance, the LoadBalancer will assume a newly registered instance is healthy and put it into the InService state. If the instance is unhealthy, it will be transitioned to the OutOfService state on the first health check. |
| 6 | You cannot charge customers for their use of Elastic Load Balancing for instances running an Amazon EC2 paid AMI. | At this time, you cannot use Elastic Load Balancing with instances running Amazon EC2 paid AMIs. |
| 7 | SOAP requests over HTTP will result in the following error: Premature end of file. AWSRequestId:No request id received. | API requests using SOAP are only supported over HTTPS. |
| 8 | The LoadBalancer does not report zeros for the RequestCount metric in Amazon CloudWatch when there are no requests. | You will get no datapoints for the RequestCount metric for the period when there are no requests. You cannot set Auto Scaling triggers that rely on zero RequestCount. |
