aws_ec2_host cost estimation
A physical server dedicated to your account, billed per host-hour by instance family. An m5 dedicated host is ~$3,700/month — you pay for the whole host, not the instances on it.
An aws_ec2_host reserves an entire physical server for your exclusive use. Unlike normal EC2 where you pay per instance, a Dedicated Host bills a flat per-host-hour rate by instance family regardless of how many instances you run on it — an m5 host is ~$5.07/hour, about $3,700/month.
Dedicated Hosts exist for specific reasons, almost always licensing and compliance: bring-your-own-license (BYOL) software licensed per physical core or socket (Windows Server, SQL Server, Oracle), regulatory requirements for physical isolation, or visibility into socket/core placement. They are not a cost optimization for general compute — for that, normal shared-tenancy instances are far cheaper.
The cost logic flips from normal EC2: because you pay for the whole host, the goal is to pack it densely. An underutilized Dedicated Host running two small instances on hardware that fits dozens is enormously wasteful. If you're not filling the host (or saving more on BYOL than the host premium costs), you probably shouldn't be on one.
c3x prices the host from instance_family at the per-host rate, so the substantial standing cost is visible before deployment.
Terraform example
A minimal but realistic configuration that C3X can estimate.
resource "aws_ec2_host" "licensed" {
instance_family = "m5"
availability_zone = "us-east-1a"
tags = {
Purpose = "byol-sql-server"
}
}Pricing dimensions
What you actually pay for when you provision aws_ec2_host.
| Dimension | Unit | What's being charged |
|---|---|---|
| Dedicated host | per hour | Flat per-host-hour rate by instance family, billed continuously regardless of how many instances run on it. ~$5.07/hour for an m5 host → ~$3,700.37/month |
Sample C3X output
An m5 Dedicated Host, 24/7:
aws_ec2_host.licensed
└─ Dedicated host (m5) 730 hours $3,700.37
Monthly $3,700.37Optimization tips
Common ways to reduce aws_ec2_host cost without changing the workload.
Only use a Dedicated Host when you actually need one
Avoid the entire host cost when shared tenancy worksDedicated Hosts are for BYOL licensing tied to physical cores/sockets, compliance isolation, or socket visibility. For general compute they're far more expensive than shared-tenancy instances — confirm the licensing/compliance saving exceeds the host premium before using one.
Pack the host densely
Proportional to host utilizationYou pay for the whole host regardless of utilization. Run as many instances on it as it physically supports — an m5 host fits many vCPUs. Two small instances on a full-size host is mostly wasted spend.
Buy a Dedicated Host Reservation for steady hosts
Up to ~70% on steady hostsDedicated Host Reservations discount the host rate by up to ~70% for a 1-3 year commitment — essential for the always-on BYOL hosts that justify a Dedicated Host in the first place.
Right-size BYOL licensing to the host
License-dependentThe point is usually license cost. Make sure the host's core/socket count matches your license entitlement so you're not paying for a host larger than the licenses you're optimizing for.
FAQ
Why is an EC2 Dedicated Host so expensive?
You pay a flat rate for an entire physical server (~$3,700/month for an m5 host), not per instance. It's priced for the dedicated hardware, so it only makes financial sense when you densely pack it or when BYOL licensing/compliance savings exceed the host premium.
When should I use a Dedicated Host?
For bring-your-own-license software licensed per physical core/socket (Windows/SQL/Oracle), regulatory physical-isolation requirements, or when you need socket/core placement visibility. Not for general compute, where shared-tenancy instances are far cheaper.
How do I reduce Dedicated Host cost?
Pack the host densely (you pay for it whole), buy a Dedicated Host Reservation for up to ~70% off on steady hosts, and confirm the host actually pays for itself via BYOL savings — otherwise move to shared-tenancy instances.
How does c3x estimate the cost?
From instance_family, pricing the per-host-hour rate. Given the scale (~$3,700/month for an m5 host), seeing the standing cost before deployment is important.
Related resources
Estimate this resource in your own Terraform
Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including aws_ec2_host.