Menu
Auto Scaling
User Guide

Troubleshooting Auto Scaling: AMI Issues

This page provides information about the issues associated with your AMIs, potential causes, and the steps you can take to resolve the issues.

To retrieve an error message, see Retrieving an Error Message.

When your EC2 instances fail to launch due to issues with your AMI, you might get one or more of the following error messages.

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:

    1. Create a new launch configuration using a valid AMI.

    2. Update your Auto Scaling group with the new launch configuration using the update-auto-scaling-group command.

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 AMI with hvm virtualization cannot be used to launch a non-cluster compute instance.

  • Solution:

    1. Create a new launch configuration using an AMI with a virtualization type of paravirtual to launch a non-cluster compute instance.

    2. Update your Auto Scaling group with the new launch configuration using the update-auto-scaling-group command.

Value (<ami ID>) for parameter virtualName is invalid.

  • Cause: Incorrect value. The virtualName parameter refers to the virtual name associated with the device.

  • Solution:

    1. Create a new launch configuration by specifying the name of the virtual device of your instance for the virtualName parameter.

    2. Update your Auto Scaling group with the new launch configuration using the update-auto-scaling-group command.

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 InstanceType mentioned in your launch configuration does not match the image architecture.

  • Solution:

    1. Create a new launch configuration using the AMI architecture that matches the architecture of the requested instance type.

    2. Update your Auto Scaling group with the new launch configuration using the update-auto-scaling-group command.