Menu
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?
996
T2 instances are Amazon EC2 instance types designed to dramatically reduce costs for applications that benefit from the ability to burst to full core performance whenever required. T2 instances are available to use in the AWS Free Tier, which includes 750 hours of Linux and Windows t2.
Linux Amazon Machine Images use one of two types of virtualization: paravirtual (PV) or hardware virtual machine (HVM). The main differences between PV and HVM AMIs are the way in which they boot and whether they can take advantage of special hardware extensions (CPU, network, and storage) for better performance.
T2 instances are Burstable Performance Instances that provide a baseline level of CPU performance with the ability to burst above the baseline. The baseline performance and ability to burst are governed by CPU Credits. Each T2 instance receives CPU Credits continuously at a set rate depending on the instance size.
T2 instances launched in Unlimited Mode do not receive launch credits. T3 and T3a instances do not get launch credits at all. If you want full power at the start, use Unlimited mode.
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.
108
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
