Submit feedback on
Stale Dedicated Hosts for Stopped EC2 Mac Instances
We've received your feedback.
Thanks for reaching out!
Oops! Something went wrong while submitting the form.
Close
Stale Dedicated Hosts for Stopped EC2 Mac Instances
Igor Bareev
Service Category
Compute
Cloud Provider
AWS
Service Name
AWS EC2
Inefficiency Type
Orphaned Resource
Explanation

When an EC2 Mac instance is stopped or terminated, its associated dedicated host remains allocated by default. Because Mac instances are the only EC2 type billed at the host level, 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

Relevant Billing Model

Billing is based on the **dedicated host reservation**, not instance runtime. Each EC2 Mac instance requires a dedicated Mac host (mac1 or mac2), which is billed per hour from allocation time — regardless of whether the instance is running, stopped, or terminated — unless the host is explicitly released.

Detection
  • 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 mac1/mac2 host usage with no active workloads associated
  • Evaluate if the use of Dedicated Host auto-release is disabled or misconfigured
Remediation
  • 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
Submit Feedback