I was referring more to the list of hypervisor features not implemented: >> Because EC2's hypervisor was (when it was launched) lacking features (no hot swap

I was referring more to the list of hypervisor features not implemented: >> Because EC2's hypervisor was (when it was launched) lacking features (no hot swap, not shared block storage, no host movements, no online backup/clone, no live recovery, no Highly available host failover ) S3 had to step in to pick up some of the slack that proper block or file storage would have taken. I don't want any of that nonsense in my compute layer or an application (at scale) that relies on shared block storage or host movements or live recovery. I'm sure S3 append would be super handy.