| « PreviousNext » | |
   | Did this page help you? Yes | No | Tell us about it... |
Troubleshooting Auto Scaling: Load Balancer Configuration
This following topics provide information about issues caused by the load balancer associated with your Auto Scaling group, potential causes, and the steps you can take to resolve the issues.
When your Amazon EC2 instances fail to launch due to issues with the load balancer associated with your Auto Scaling group, you might get one or more of the error messages covered in the following topics. To retrieve the error message and review the error message lists sorted by the type of issue, see Retrieving an Error Message.
Before you begin troubleshooting issues with the load balancer configurations, be sure you've installed the Elastic Load Balancing interface you plan to use to access your load balancer. For more information, go to Get Set Up With Elastic Load Balancing Interfaces in the Elastic Load Balancing Developer Guide.
Cannot find Load Balancer <your launch environment>. Validating load balancer configuration failed.
Cause 1: The load balancer has been deleted.
Solution 1:
Check to see if your load balancer still exists. You can use either the DescribeLoadBalancer action or the
elb-describe-lbscommand.If you see your load balancer listed in the response, see Cause 2.
If you do not see your load balancer listed in the response, you can either create a new load balancer and then create a new Auto Scaling group or you can create a new Auto Scaling group without the load balancer.
Cause 2: The load balancer name was not specified in the right order when creating the Auto Scaling group.
Solution 2: Create a new Auto Scaling group and specify the load balancer name at the end.
There is no ACTIVE Load Balancer named <load balancer name>. Updating load balancer configuration failed.
Cause: The specified load balancer might have been deleted.
Solution: You can either create a new load balancer and then create a new Auto Scaling group or create a new Auto Scaling group without the load balancer.
EC2 instance <instance ID> is not in VPC. Updating load balancer configuration failed.
Cause: The specified instance does not exist in Amazon VPC.
Solution: You can either delete your load balancer associated with the instance or create a new Auto Scaling group.
The security token included in the request is invalid. Validating load balancer configuration failed.
Cause: Your AWS account might have expired.
Solution: Check if your AWS account is valid. Go to http://aws.amazon.com and click the Sign Up Now button to open a new account.
