Why do Spot Instances(EC2) change from cancelled_terminating to cancelled?

Question

I have been struggling with this since last 2 days -

A. Trying to create AWS Spot Instance with Deep Learning AMI for Linux (free).
B. Upon launching EC2 Instance it says Spot Instance request successfully created but it fails to create the instance.
C. Using Spot Fleet role, and later have been trying to change it to provide Admin access to this role through Policies.

However, the instance is never created and in the History tab I see Event Type = fleetRequestChange goes from Submitted , active , cancelled_terminating within a minute and later cancelled .

I have been reading through its documentation but don't see a reason for it to fail. Verified the Region and AMI as well. Tried changing bid price and with default recommended option as well. But nothing seems to work.

This is the link I'm referring - AWS setup for Deep Learning

Please skip the initial portion of getting credits and you can directly jump to EC2 instance configuration setup.

Kindly help! I am unable to proceed for the past 2 days.

Thank you!

Answer 1

It worked perfectly fine for me.

• Launched the Deep Learning AMI (ami-df77b6a7) in the Oregon region
• Spot pricing as documented in the article you referenced
• I could ssh into the instance after it launched

One thing you could check... Click the Limits link in your EC2 console to confirm that you can launch this type of instance.

Mine said:

• Running On-Demand g2.2xlarge instances: 5