![]() But this can only be done using the AWS CLI, not through the UI. Technically speaking: An additional attribute "EnaSupport" needs to be added to the instance. The AWS EC2 instance itself needs to be told it is ENA-ready as well. Obviously my "quick read" led me into thinking that only the Linux Kernel must be ready for the new interface type. If this Kernel module would not be on the system, the instance would (most likely) not start up correctly.īut a click on "Yes, Start" didn't help. Parm: debug:Debug level (0=none.,16=all) (int) Vermagic: 4.4.0-142-generic SMP mod_unload modversions retpoline I quickly read through the " Enabling enhanced networking with the Elastic network adapter" guide and verified on another still running instance if the Kernel module exists in that Ubuntu (16.04) modinfo enaįilename: /lib/modules/4.4.0-142-generic/kernel/drivers/net/ethernet/amazon/ena/ena.koĭescription: Elastic Network Adapter (ENA)Īuthor:, Inc. Ensure that your instance 'i-073XXXXXXXXXXXXXX' is enabled for ENA. But got this error message popping up instead:Įnhanced networking with the Elastic Network Adapter (ENA) is required for the 't3.2xlarge' instance type. ![]() After change of instance type, failure to startĪfter shutdown of the instance, I changed the instance type and wanted to start it. However during "normal runtime" the CPU usage is pretty steady. We see CPU spikes whenever a deployment happens and new containers are rolled out/upgraded. This does sound interesting and is actually what we need. Opportunity to burst with the performance of a full CPU core for one Each earned CPU credit provides the T3 instance the T3 instances accumulate CPU credits when a workload is operating belowīaseline threshold. M4/M5 instances provide a balance of compute, memory, and network resources, and it is a good choice for many applications. ![]() The instance type description explain the difference between M and T instances this way: But the t3.2xlarge instance type caught my attention as it offers the same capacity specs but is cheaper than the m4 equivalent. Well to narrow down the list, I compared some of the newer instances with the type we currently run (m4.xlarge):īy choosing the "logical" bigger instance (m4.2xlarge) we would pay exactly the double per hour. It feels like being in a candy shop where all you see is candy and you want to try them all. It's 2019 and wow, there are so many new instance types. Some of our EC2 instances, used as Docker hosts, started to use up the instances capacities. Cannot start AWS EC2 instance after changing instance type: Ensure that your instance is enabled for ENA
0 Comments
Leave a Reply. |