.metal Instance vs .metal instance on Dedicated Host

Question

Hello.

I'd like to ask whether or not any merit to use .metal instance on Dedicated Host, instead of creating and using EC2 .metal instance.

When allocating Dedicated Host, Instance Family and Instance Type can be set, and .metal instance can be running on the Dedicated Host when setting Instance type to .metal.

It seems that both .metal Instance and the same baremetal instance on Dedicated Host works very similar. What's difference between these? As far as I know, both provide a non-hypervisor physical host with full usability of physical resource, aka. CPU, memory, and so on.

Thanks in advance.

Answer

Bare-metal instances are introduced as having access to hardware but are not described as occupying hardware. Therefore, we assume that bare-metal instances provide access to hardware while sharing hardware with Nitro System.

I could not find any clear documentation. The following document has a link to the video "AWS re:Invent 2017: Amazon EC2 Bare Metal Instances". This may be of some help.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html

If you choose Dedicated Hosts, you will be provided with a physical server that is completely dedicated to you, as described in the following document.

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-overview.html

.metal Instance vs .metal instance on Dedicated Host

Conteúdo relevante