Presentation: Troubleshooting EC2 Instance Launch Issues

EC2 Instance Launch Troubleshooting

1. InstanceLimitExceeded Error

• Cause: Reached the maximum number of vCPUs per region.
• Resolution:
  • Launch the instance in a different region.
  • Request AWS to increase your vCPU limit in the region.
• When you launch an EC2 instance and you get this error InstanceLimitExceeded, then you have reached your limit of a maximum number of vCPUs per AWS Region. Either launch the EC2 instance in a different AWS Region or contact AWS Support to increase your limit of the AWS Region.

How to Check vCPU Limits

• Navigate to Limits in the EC2 console.
• Look for vCPU limits for On-Demand and Spot instances.
• Default Limits:
  • All Standard Spot Instance Requests: 64 vCPUs
  • Running On-Demand All Standard Instances: 64 vCPUs
• To request an increase, click on "Request a limit increase".

Service Quotas Console

• Use the Service Quotas console to view and request increases for various limits.

vCPU Allocation by Instance Type

• Go to Launch Instance > Instance Type > Compare Instance Types.
• Example:
  • t2.micro: 1 vCPU
  • c5.9xlarge: 36 vCPUs

2. InsufficientInstanceCapacity Error

• Cause: AWS does not have enough capacity for On-Demand instances in the selected Availability Zone (AZ).
• Resolution:
  • Wait and retry later if more capacity becomes available.
  • Request fewer instances at a time.
  • Choose a different instance type and resize later if needed.
  • Try launching in a different AZ.

3. Instance Terminates Immediately