Release: Elastic Load Balancing on 2010-04-28
Adds support for the Asia Pacific (Singapore) region.
Elastic Load Balancing now supports the Asia Pacific (Singapore) Region. The new endpoint for requests
to this Region is http://elasticloadbalancing.ap-southeast-1.amazonaws.com.
|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 for each port. Moreover, for LoadBalancers with TCP listeners, the Latency metric is not a meaningful measure of the TCP
|Any attempt to register a paid AMI as an instance behind an ELB will fail.
||At this time, you cannot use Elastic Load Balancing with instances running Amazon EC2 paid AMIs.
|API requests using SOAP are only supported over HTTPS.
||SOAP requests over HTTP will result in the following error: Premature end of file. AWSRequestId:No request id received.
|The LoadBalancer does not report zeros for the RequestCount metric in Amazon CloudWatch when there are no requests.
||The RequestCount metric doesn't provide a zero (0) datapoint for periods that have no requests.