Hands-on AWS knowledge base for developers Managed Ops
Talk to Us

EC2 Dedicated Host vs Dedicated Instance: Real Differences

Export PDF Print-friendly layout with a copyright watermark; choose Save as PDF in the print dialog
EC2 Dedicated Host vs Dedicated Instance: Real Differences

TL;DR

  • A dedicated instance is a normal EC2 instance whose physical server is reserved for your account only. You never see that server, and Placement.Tenancy reads dedicated.
  • A Dedicated Host is an entire physical server billed to you by the hour. Placement.Tenancy reads host, and describe-hosts exposes sockets, cores and free slots — the numbers socket-based licensing audits run on.
  • The cost curve flips. Dedicated instances scale with instance count; a host bills whether you put one instance on it or none.

Two CLI outputs that tell you which tenancy you actually bought

Start at the destination. Whichever path you take, this is the command that proves what you're paying for:

aws ec2 describe-instances 
  --instance-ids i-0123456789abcdef0 
  --query 'Reservations[].Instances[].Placement'


Dedicated instance:

```json
[{"AvailabilityZone":"us-east-1a","Tenancy":"dedicated"}]


Dedicated Host:

```json
[{"AvailabilityZone":"us-east-1a","Tenancy":"host","HostId":"h-0f3c9a1b2d4e5f678"}]


If the field says `default`, you bought neither and the instance is sharing hardware as usual. Everything below is about producing one of those two outputs deliberately, from a console click or a script.

## Dedicated Host vs dedicated instance: what the difference actually buys

| Dimension | Dedicated instance | Dedicated Host |
|---|---|---|
| `Placement.Tenancy` | `dedicated` | `host` + `HostId` |
| Hardware visibility | None | Sockets, cores, vCPUs, free slots |
| Who picks the physical box | AWS | You (explicit `HostId` or auto-placement) |
| BYOL measured by socket/core | No | Yes — this is the whole point |
| Instance types allowed | Broad | One family per host, subset of types |
| Billing unit | Per instance-hour, at a premium over shared | Per host-hour, independent of load |
| Capacity guarantee | No — you can still hit insufficient capacity | Yes, if a slot is free on your host |
| Teardown | Terminate the instance | Stop instances, then `release-hosts` |

Licensing is what decides most small deployments. If you run Windows Server or SQL Server under your own agreement, a dedicated instance gives you nothing to point at during an audit — you still can't prove which cores belong to you. A host hands you the socket count directly

Sources

Leave a Reply

Your email address will not be published. Required fields are marked *