Explanation
Why the waste happens and who it affects.
Because Mac instances run only on Dedicated Hosts (one instance per host) and the host, not the instance, is the unit of billing, charges continue to accrue as long as the host is retained. This can lead to significant waste when:
- Instances are stopped but the host is never released
- Hosts are retained unintentionally after workloads are migrated or decommissioned
- Automation only terminates instances without deallocating hosts
Billing model
The pricing dimensions that drive this cost.
Billing is based on the dedicated host reservation, not instance runtime. Each EC2 Mac instance requires a dedicated Mac host (such as mac1, mac2, mac2-m2pro or mac-m4), which is billed per second from allocation time (with a 24-hour minimum allocation period before the host can be released) - regardless of whether the instance is running, stopped, or terminated - unless the host is explicitly released.
How to detect
4 checks to find it in your estate.
- Review whether any EC2 Mac dedicated hosts remain allocated without a running instance
- Check for host reservations persisting beyond expected lifespans (e.g., post-project teardown)
- Identify cost entries for Mac host usage with no active workloads associated
- Check whether teardown automation releases hosts (ReleaseHosts) once the 24-hour minimum allocation period has passed, since Dedicated Hosts are never released automatically
How to fix
4 ways to remove the waste.
- Release Mac dedicated hosts after stopping or terminating Mac EC2 instances if no longer needed
- Update automation workflows to include host deallocation logic when applicable
- Enable lifecycle tracking of dedicated hosts to avoid forgotten allocations
- Where appropriate, consolidate Mac workloads to minimize the number of hosts in use
Documentation
Vendor references for pricing and configuration.