Billing and cost Mac m2 Istance

Question

Hi,

I'm trying to set up a macOS instance to deploy Apple apps without purchasing dedicated hardware, and I'm looking to minimize costs.

I've researched and been told that Mac instances are billed with a minimum of 24 hours, and that stopping the instance prevents further charges.  However, I created a dedicated host and launched a Mac instance, and even though the instance was stopped, I was charged about $50 over three days.

I'm confused about whether the billing is based on the dedicated host's uptime or the instance's uptime. Could someone clarify this for me?

Also, if anyone has experience with this and could share the most cost-effective strategy for achieving this, I'd greatly appreciate it.
Thanks!

re:Post Agent · Accepted Answer

I understand your confusion regarding the billing for EC2 Mac instances. Let me clarify this for you.

For EC2 Mac instances, the billing is based on the dedicated host allocation, not the instance's uptime. This means you are charged for the time the physical Mac mini (dedicated host) is reserved for your use, regardless of whether the EC2 instance running on it is started or stopped.

The key points to understand are:

1. You must allocate a dedicated host to run a Mac instance. This host is exclusively used by your AWS account.

2. The billing starts when you allocate the dedicated host and continues until you release it, even if the EC2 instance on that host is stopped.

3. There is a minimum allocation period of 24 hours for the dedicated host due to Apple's macOS license agreement. You cannot release the host before this 24-hour period ends.

4. After the initial 24-hour period, you can release the host at any time, which will stop the billing.

To minimize costs, the most effective strategy would be:

1. Plan your work efficiently to utilize the dedicated host as much as possible within each 24-hour period.

2. Release the dedicated host as soon as you're done with your work and after the initial 24-hour period has passed.

3. If you need the environment again, allocate a new dedicated host when required.

4. Consider using Savings Plans if you have a consistent workload, as they can offer up to 44% savings compared to On-Demand pricing.

Remember, simply stopping the EC2 instance does not stop the charges - you must release the dedicated host to end billing. This explains why you were charged over three days despite stopping the instance.

For occasional use, it's best to allocate the host, do your work within 24 hours if possible, and then release the host. For more frequent or longer-term use, explore Savings Plans to reduce costs.  
**Sources**  
[Community | Start an Amazon EC2 Mac instance](https://community.aws/content/2duUEgh4u4TIDqfECiDkEbrn2Iw/ec2-mac-01-start-an-ec2-mac-instance)  
[Community | Start an Amazon EC2 Mac instance](https://community.aws/tutorials/ec2-mac/01-start-an-ec2-mac-instance)  
[Amazon EC2 FAQs - Amazon Web Services](https://aws.amazon.com/ec2/instance-types/mac/faqs/)  
[Amazon EC2 Mac Instances - Amazon Web Services](https://aws.amazon.com/ec2/instance-types/mac/)

Quadra_Dev · Answer

Is there a way to create a custom macOS instance with the desired configuration and then relaunch it as needed, potentially reallocating a new dedicated host each time?

Billing and cost Mac m2 Istance

Add your answer

Relevant content