- 최신
- 최다 투표
- 가장 많은 댓글
Amazon EC2 Metal instances provide you with physical CPUs, not virtualized CPUs. Metal instances are not virtualized; they do not run under a hypervisor like non-Metal instances do. We do use the same "vCPU" terminology in our APIs and the EC2 Console even with Metal instances, but rest assured you will have full access to all CPU resources.
Just a point of clarity - EC2 Dedicated Hosts are different from Metal instances. EC2 Dedicated Hosts are intended to run multiple EC2 instances on the same physical machine; you allocate a Dedicated Host and then can assign EC2 instances to that host. Dedicated Hosts are not EC2 instances themselves; you cannot run workloads on them or access them until you assign instances to them. Metal instances, on the other hand, are EC2 instances mapped to entire physical hosts that cannot be subdivided into multiple EC2 instances. (You can even run your own hypervisor on Metal instances if you like, which is something you cannot do with non-Metal instances.)
Hello,
I think that you want to read https://docs.aws.amazon.com/whitepapers/latest/security-design-of-aws-nitro-system/the-components-of-the-nitro-system.html especially the "Nitro hypervisor" section to understand why AWS still speaks of vCPU with bare metal instances.
If you are not familiar with Nitro, you may want to start here: https://aws.amazon.com/ec2/nitro/
Best,
Didier
Thank you @MichaelFischer! So, to allocate bare metal instances without going through the EC2 Dedicated Host, what should I do, please? Which instance type should I choose?
I think I found them. They are *.metal, right? e.g., m5d.metal. But one interrogation remains: are there such metal instances with GPUs? I can't find some on EC2
We offer two GPU-enabled instance types today in bare metal configurations: G4dn.metal and G5g.metal.
Yes, I had already found them. Many thanks!