Troubleshoot Amazon EC2 Auto Scaling: EC2 instance launch failures

Cause: Some options in your launch template or launch configuration might not be compatible with the instance type, or the instance configuration might not be supported in your requested Amazon Region or Availability Zones.

Solution:

Try a different instance configuration. To search for an instance type that meets your requirements, see Finding an Amazon EC2 instance type in the Amazon EC2 User Guide for Linux Instances.

For further guidance to resolve this issue, check the following:

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

Solution:

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

Solution:

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.

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 you chose 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.

Cause: The Spot maximum price in your request is lower than the Spot price for the instance type that you selected.

Solution: Submit a new request with a higher Spot maximum price (possibly the On-Demand price). Previously, the Spot price you paid was based on bidding. Today, you pay the current Spot price. By setting your maximum price higher, it gives the Amazon EC2 Spot service a better chance of launching and maintaining your required amount of capacity.

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

Solution:

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:

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

Solution:

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

Solution:

Problem: Amazon EC2 Auto Scaling tries to launch an instance that has an encrypted EBS volume, but the service-linked role does not have access to the Amazon KMS customer managed key used to encrypt it. For more information, see Required Amazon KMS key policy for use with encrypted volumes.

Cause 1: You need a key policy that gives permission to use the customer managed key to the proper service-linked role.

Solution 1: Allow the service-linked role to use the customer managed key as follows:

For an example of a key policy that lets the service-linked role use the customer managed key, see Example 1: Key policy sections that allow access to the customer managed key.

Cause 2: If the customer managed key and Auto Scaling group are in different Amazon accounts, you need to configure cross-account access to the customer managed key in order to give permission to use the customer managed key to the proper service-linked role.

Solution 2: Allow the service-linked role in the external account to use the customer managed key in the local account as follows:

For more information, see Example 2: Key policy sections that allow cross-account access to the customer managed key.

Solution 3: Use a customer managed key in the same Amazon account as the Auto Scaling group.

Error message: We currently do not have sufficient <instance type> capacity in the Availability Zone you requested (<requested Availability Zone>). Our system will be working on provisioning additional capacity. You can currently get <instance type> capacity by not specifying an Availability Zone in your request or choosing <list of Availability Zones that currently supports the instance type>. Launching EC2 instance failed.

Cause: At this time, Amazon EC2 cannot support your instance type in your requested Availability Zone.

Solution:

To resolve the issue, try the following:

Cause: At this time, there isn't enough spare capacity to fulfill your request for Spot Instances.

Solution:

To resolve the issue, try the following:

Cause: You have reached the limit on the number of instances that you can launch in a Region. When you create your Amazon account, we set default limits on the number of instances you can run on a per-Region basis.

Solution:

To resolve the issue, try the following: