Menu
Amazon EC2 Auto Scaling
User Guide

Troubleshooting Amazon EC2 Auto Scaling: EC2 Instance Launch Failures

This page provides information about your EC2 instances that fail to launch, 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, you might get one or more of the following error messages:

The security group <name of the security group> does not exist. Launching EC2 instance failed.

  • Cause: The security group specified in your launch configuration might have been deleted.

  • Solution:

    1. Use the describe-security-groups command to get the list of the security groups associated with your account.

    2. From the list, select the security groups to use. To create a security group instead, use the create-security-group command.

    3. Create a new launch configuration.

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

The key pair <key pair associated with your EC2 instance> does not exist. Launching EC2 instance failed.

  • Cause: The key pair that was used when launching the instance might have been deleted.

  • Solution:

    1. Use the describe-key-pairs command to get the list of the key pairs available to you.

    2. From the list, select the key pair to use. To create a key pair instead, use the create-key-pair command.

    3. Create a new launch configuration.

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

The requested configuration is currently not supported.

  • Cause: Some options in your launch configuration might not be currently supported.

  • Solution:

    1. Create a new launch configuration.

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

AutoScalingGroup <Auto Scaling group name> not found.

  • Cause: The Auto Scaling group might have been deleted.

  • Solution: Create a new Auto Scaling group.

The requested Availability Zone is no longer supported. Please retry your request...

  • Error Message: The requested Availability Zone is no longer supported. Please retry your request by not specifying an Availability Zone or choosing <list of available Availability Zones>. Launching EC2 instance failed.

  • Cause: The Availability Zone associated with your Auto Scaling group might not be currently available.

  • Solution: Update your Auto Scaling group with the recommendations in the error message.

Your requested instance type (<instance type>) is not supported in your requested Availability Zone (<instance Availability Zone>)...

  • Error Message: Your requested instance type (<instance type>) is not supported in your requested Availability Zone (<instance Availability Zone>). Please retry your request by not specifying an Availability Zone or choosing <list of Availability Zones that supports the instance type>. Launching EC2 instance failed.

  • Cause: The instance type associated with your launch configuration might not be currently available in the Availability Zones specified in your Auto Scaling group.

  • Solution: Update your Auto Scaling group with the recommendations in the error message.

You are not subscribed to this service. Please see http://aws.amazon.com.

  • Cause: Your AWS account might have expired.

  • Solution: Go to http://aws.amazon.com and choose Sign Up Now to open a new account.

Invalid device name upload. Launching EC2 instance failed.

  • Cause: The block device mappings in your launch configuration might contain block device names that are not available or currently not supported.

  • Solution:

    1. Use the describe-volumes command to see how the volumes are exposed to the instance.

    2. Create a new launch configuration using the device name listed in the volume description.

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

Value (<name associated with the instance storage device>) for parameter virtualName is invalid...

  • Error Message: Value (<name associated with the instance storage device>) for parameter virtualName is invalid. Expected format: 'ephemeralNUMBER'. Launching EC2 instance failed.

  • Cause: The format specified for the virtual name associated with the block device is incorrect.

  • Solution:

    1. Create a new launch configuration by specifying the device name in the virtualName parameter. For information about the device name format, see Instance Store Device Names in the Amazon EC2 User Guide for Linux Instances.

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

EBS block device mappings not supported for instance-store AMIs.

  • Cause: The block device mappings specified in the launch configuration are not supported on your instance.

  • Solution:

    1. Create a new launch configuration with block device mappings supported by your instance type. For more information, see Block Device Mapping in the Amazon EC2 User Guide for Linux Instances.

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

Placement groups may not be used with instances of type 'm1.large'. Launching EC2 instance failed.

  • Cause: Your cluster placement group contains an invalid instance type.

  • Solution:

    1. For information about valid instance types supported by the placement groups, see Placement Groups in the Amazon EC2 User Guide for Linux Instances.

    2. Follow the instructions detailed in the Placement Groups to create a new placement group.

    3. Alternatively, create a new launch configuration with the supported instance type.

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

Client.InternalError: Client error on launch.

  • Cause: This error can be caused when an Auto Scaling group attempts to launch an instance that has an encrypted EBS volume, but the service-linked role does not have access to the customer managed CMK used to encrypt it.

  • Solution: Additional setup is required to allow the Auto Scaling group to launch instances. The table below summarizes the steps to follow to resolve the error. For detailed instructions, see https://forums.aws.amazon.com/thread.jspa?threadID=277523.

Scenario Next Steps

Scenario 1:

CMK and Auto Scaling group are in the same AWS account

Allow the service-linked role to use the CMK as follows:

  1. Determine which service-linked role to use for this Auto Scaling group.

  2. Update the key policy on the CMK to allow the service-linked role to use the CMK.

  3. Update the Auto Scaling group to use the service-linked role.

Scenario 2:

CMK and Auto Scaling group are in different AWS accounts

There are two possible solutions:

Solution 1: Use a CMK in the same AWS account as the Auto Scaling group

  1. Copy and re-encrypt the snapshot with another CMK that belongs to the same account as the Auto Scaling group.

  2. Allow the service-linked role to use the new CMK. See the steps for Scenario 1.

Solution 2: Continue to use the CMK in a different AWS account from the Auto Scaling group

  1. Determine which service-linked role to use for this Auto Scaling group.

  2. Allow the Auto Scaling group account (root user) access to the CMK.

  3. Define an IAM user or role in the Auto Scaling group account to create a grant.

  4. Create a grant to the CMK with the service-linked role as the grantee principal.

  5. Update the Auto Scaling group to use the service-linked role.