Virtualization type 'hvm' is required for instances of type 't2.micro'

Question

Seems selecting t2.micro for an ElasticBeanstalk instance throws Beanstalk into an infinite loop. Been an hour since creating the Beanstalk instance, 20min since the last event update in the Beanstalk management console. Does anyone know how to kill a Beanstalk instance deploy?

Accepted Answer

Turns out this is what happens when you try to take a t1 (ParaVirtualization) AMI and deploy it on a t2 (HVM) ElasticBeanstalk instance. The Beanstalk instance failed/retried for about an hour and a half before it finally errored out.

Virtualization type 'hvm' is required for instances of type 't2.micro'

Solution

Problem