| « PreviousNext » | |
   | Did this page help you? Yes | No | Tell us about it... |
Troubleshooting Auto Scaling: Amazon EC2 AMIs
The following topics provide information about the issues associated with your Amazon EC2 images, potential causes, and the steps you can take to resolve the issues.
When your Amazon EC2 instances fail to launch due to issues with your AMIs, 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.
The AMI ID <ID of your AMI> does not exist. Launching EC2 instance failed.
Cause: The AMI might have been deleted after creating the launch configuration.
Solution:
Create a new launch configuration using a valid AMI.
Update your Auto Scaling group with the new launch configuration using the UpdateAutoScalingGroup action or the
as-update-auto-scaling-groupcommand.
AMI <AMI ID> is pending, and cannot be run. Launching EC2 instance failed.
Cause: You might have just created your AMI (by taking a snapshot of a running instance or any other way), and it might not be available yet.
Solution: You must wait for your AMI to be available and then create your launch configuration.
Non-Windows AMIs with a virtualization type of 'hvm' currently may only be used with Cluster Compute instance types. Launching EC2 instance failed.
Cause: The Linux/UNIX AMI with hvm virtualization cannot be used to launch a non-cluster compute instance.
Solution:
Create a new launch configuration using an AMI with a virtualization type of paravirtual to launch a non-cluster compute instance.
Update your Auto Scaling group with the new launch configuration using the UpdateAutoScalingGroup action or the
as-update-auto-scaling-groupcommand.
Value (<ami ID>) for parameter virtualName is invalid.
Cause: Incorrect value. The
virtualNameparameter refers to the virtual name associated with the device.Solution:
Create a new launch configuration by specifying the name of the virtual device of your instance for the
virtualNameparameter.Update your Auto Scaling group with the new launch configuration using the UpdateAutoScalingGroup action or the
as-update-auto-scaling-groupcommand.
The requested instance type's architecture (i386) does not match the architecture in the manifest for ami-6622f00f (x86_64). Launching ec2 instance failed.
Cause: The architecture of the
InstanceTypementioned in your launch configuration does not match the image architecture.Solution:
Create a new launch configuration using the AMI architecture that matches the architecture of the requested instance type.
Update your Auto Scaling group with the new launch configuration using the UpdateAutoScalingGroup action or the
as-update-auto-scaling-groupcommand.
