Re:Unfashionably secure: why we use isolated VMs
by kasey_junk on Thursday July 25, 2024 @10:19PM
(#41075323)
I think the argument is you need to be running nitro (I think, itβs been awhile?) instances to take advantage of kvm isolation
Re:Unfashionably secure: why we use isolated VMs
by ryapric on Thursday July 25, 2024 @10:21PM
(#41075331)
>What I'm I missing?
The parent isn't talking about e.g. EC2 as a virtualized platform, they're talking about EC2 not being a virtualization platform. With few machine-type exceptions, EC2 doesn't support nested virtualization -- you can't run e.g. KVM on EC2.
And I've been at a few shops where EC2 is used as the poor-man's-firecracker by building containers and then running 1(ish) per VM. AWS's architecture actively encourages this because that's by far the easiest security boundary to manipulate. The moment you start thinking about two privilege levels in the same VM you're mostly on your own.
The number of people running production workloads who, knowingly or not, believe that the security boundary is not between containers but between the vms enclosing those containers is probably almost everyone.