title: Confusion about instances used inside a Amazon Ec2 Container Service
body: <p>When a Ec2 Container Engine cluster is created, it creates a Compute Engine managed instance group to manage the created instances. These instances are from Ec2 service, which means, they are Virtual machines.</p>
  
  <p>But we know that containers represent a new way to deploy containers based on operating-system-level virtualization rather than hardware virtualization
  like VMs that are heavyweight and non-portable, isn't a contradiction? correct me if I'm wrong. </p>
  
  <p>We use containers because they are extremely fast (either in boot time or tasks execution) compared to VMs, and they save a lot of space storage. So if we have one node(vm) that can supports 4 containers max, our clients can rapidly lunch 4 containers, but beyond this number, Ec2 autoscaler will need to lunch a new node(vm) to support upcoming containers, which incurs some tasks delay.</p>
  
  <p>Is it impossible to launch containers over physical machines?</p>
  
  <p>And what do you recommend for running critical time execution tasks?</p>