Opportunity Name:
EC2 Release Unused Dedicated Hosts
AWS Resource Type:
EC2 (Dedicated Hosts)
Opportunity Description:
An EC2 Dedicated Host is billed for every hour it is allocated, whether or not it is running any instances. This opportunity identifies Dedicated Hosts that have carried no instances for an extended period and recommends releasing them to eliminate that host-hour cost entirely.
Criteria for identifying the opportunity:
- The host currently exists and is in a releasable allocation state.
- The host is carrying no instances right now.
- The host was allocated more than the lookback window ago (so a host you just stood up is never flagged).
- The host is not covered by a Host Reservation (a reservation commits you to the host regardless of use, so releasing it would not reduce your bill).
- No instance has been launched onto the host at any point across the lookback window — CloudFix checks CloudTrail directly for this, since Dedicated Hosts have no CloudWatch occupancy metric to read.
Lookback window:
You can choose how long a host must have been empty before CloudFix recommends releasing it: 2, 7 (default), or 30 days. A longer window is a more conservative bar — fewer hosts qualify, but you have more confidence none of them will be needed again soon.
Potential savings (range in % on annual basis):
- 100% of the released host's ongoing host-hour cost — there is no partial saving, since an empty host provides no value.
Can CloudFix implement the fix automatically once I accept the recommendation?
No. Releasing a Dedicated Host is a physical-capacity action: it returns the underlying server to AWS's pool, so it needs your explicit sign-off. Before releasing a host, confirm no scheduled or seasonal workload targets it, and if the host is associated with a License Manager host resource group, unlink it from that group first.
Other considerations:
- This finder is recommendation-only and does not modify or delete anything in your account.
- A released host cannot be un-released — if you need dedicated capacity again later, you allocate a new host, which may or may not be the identical physical server.
- If the host carries software licensed per-socket or per-core to a specific physical host (for example some Windows Server or SQL Server BYOL terms), confirm your license terms before releasing.
Bill Gleeson
Comments